release-version-reminder-bot
Open
- Dominant language
- JavaScript
- Stars
- 9
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
At time of writing, no GAP actually has a published version!
We should nag GAP authors that if there is no published version 4 weeks after the draft has been updated, then you should release a new version
(resets when the draft is updated again)
Ideally this would in the form of a draft PR that is auto-created and assigned to the GAP author(s) to merge.
Contributor guide
Research direction
No file or test is named. Start by mapping the repository's GAP draft-update workflow and any existing GitHub automation; then determine how the four-week reminder and reset should be represented. Done means an eligible GAP produces an author-assigned draft PR, while a later draft update prevents the previous reminder from applying.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100