This came up in the Discord and I added it as a comment on the Freshenable Collections blog post for posterity but I thought I’d share here as well. (By “thought I’d” I mean I have a beemergency to move something that was valuable in the Discord to the forum.)
My workflow for gissue (GitHub Issue) freshening:
- Go to the repo, eg, http://github.com/beeminder/road. (I have a Raycast shortcut for lots of common URLs like that.)
- Click the Quick Link I added at the top of the README, which sorts gissues by staleness and filters for non-snoozed: https://github.com/beeminder/road/issues?q=is:issue+is:open+sort:updated-asc+-label:ZzZ
- Freshen however many gissues Beeminder is telling me I have to.
- Manually enter that number in my Beeminder do-more goal.
It’s great. Quick review: Sometimes you have a backlog you need to whittle down, and a whittle-down Beeminder goal is great for that. But other times you just have an evergrowing collection of drafts or notes or tickets in an issue tracker for improvements or bug fixes. It’s expected that you’ll had to it faster than you’ll dispatch things, but you don’t want it to be a place where new ideas go to die. That’s where freshening comes in.