keybase / keybase/keybase-issues
Clean out the issues
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
At the moment of writing there are 1839 open issues, the oldest last updated in 2014.
I understand that this is most likely because Keybase uses a different internal issue tracker, but as a consumer it doesn't inspire confidence in the product.
Perhaps you could install an issue bot that auto-closes issues after a warning? They can always be reopened.
Same with those 118 PRs in keybase client, perhaps auto-close really old ones with merge conflicts?
(same as https://github.com/keybase/client/issues/18503)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing this issue and the referenced keybase/client#18503, then inspect the repository's current issue and pull-request backlog. Define the warning and auto-close behavior for old issues and pull requests, including how reopening should work. Done means an agreed, documented automation policy is implemented or this issue is closed with a clear decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100