release-version-reminder-bot

Open
#59 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript
Domain
devops, release

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.

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.

Dominant language
JavaScript
Stars
10
Forks
8
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from graphql/gaps

All issues in graphql/gaps

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.