docs(watchers): list aw-watcher-ask-away and aw-watcher-checkin - #180
Conversation
aw-watcher-ask-away (Jeremiah England) asks what you were doing when you return from an AFK break; it was not listed. It has been adopted into the ActivityWatch org as aw-watcher-checkin, with full history and attribution, to be extended with boundary-triggered check-ins. Both are placed next to the related aw-watcher-ask entry under Other watchers.
 The documentation-only change is safe to merge after a non-blocking wording correction clarifies which Findings
|
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| - :gh:`akohlbecker/aw-watcher-tmux` - A plugin for tmux that allows monitoring activity in sessions and panes, by :gh-user:`akohlbecker` | ||
| - :gh:`bcbernardo/aw-watcher-ask` - (WIP) Periodically poses questions to the user and records her answers. | ||
| - :gh:`Jeremiah-England/aw-watcher-ask-away` - Asks what you were doing when you return from an AFK break, and logs it as the AFK period, by :gh-user:`Jeremiah-England`. | ||
| - :gh-aw:`aw-watcher-checkin` - (WIP) Boundary-triggered check-ins: rate the block you just finished when you return from AFK, switch context, or end a long block. Adopted from :gh:`Jeremiah-England/aw-watcher-ask-away` with full history, by :gh-user:`Jeremiah-England`. |
There was a problem hiding this comment.
This entry describes AFK-return, context-switch, and long-block triggers as current behavior, but the PR description says aw-watcher-checkin is only “to be extended” with boundary-triggered check-ins. The (WIP) label does not make clear that these specific features are planned, so readers may install the watcher expecting functionality that is not available yet. Please separate the inherited behavior from the planned triggers.
| - :gh-aw:`aw-watcher-checkin` - (WIP) Boundary-triggered check-ins: rate the block you just finished when you return from AFK, switch context, or end a long block. Adopted from :gh:`Jeremiah-England/aw-watcher-ask-away` with full history, by :gh-user:`Jeremiah-England`. | |
| - :gh-aw:`aw-watcher-checkin` - (WIP) Adopted from :gh:`Jeremiah-England/aw-watcher-ask-away` with full history, by :gh-user:`Jeremiah-England`. Boundary-triggered check-ins for AFK returns, context switches, and long blocks are planned. |
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
There was a problem hiding this comment.
Fixed in 0f497de — inherited AFK-return is current; context-switch and long-block are marked planned.
…riggers Greptile P2 on ActivityWatch#180: the WIP line listed context-switch and long-block as current behavior. Keep the inherited ask-away prompt as what ships now; mark the extra triggers as planned.
2 participants
Adds two entries under Other watchers, next to the existing
aw-watcher-askline:Jeremiah-England/aw-watcher-ask-away— asks what you were doing when you return from an AFK break and logs it as the AFK period. Was not listed.ActivityWatch/aw-watcher-checkin— the org adoption of the above (full history preserved, attribution in-repo), to be extended with boundary-triggered check-ins. Marked WIP.Requested by @ErikBjare as part of adopting
aw-watcher-ask-awayinto the org.