open-feature / open-feature/community
[CHORE] Automate stale-issue detection and closure where appropriate
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 104
- Forks
- 103
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 3
Description
We should build some automation to mark issues as stale, ping users, and perhaps auto-close things.
I think we can (and should) do this on the org-level with a solution like this: https://github.com/actions/stale/discussions/1089#discussioncomment-7239931, however, I would advocate we should just host this code ourselves in the community-tooling repo, since this involves the use of a custom fork of another popular action.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked actions/stale discussion and the community-tooling repository context. Define the required org-level behavior for marking issues stale, notifying users, and closing them, then determine how the custom fork would be hosted and maintained; done means the agreed automation is deployed and its behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100