TooAngel / TooAngel/worlddriven
Update the status check more often and write a comment
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 18
- Forks
- 15
- Avg merge
- 8d 14h
- Merged PRs (30d)
- 5
Description
When a github webhook is triggered the github commit status should be updated and a comment should be written to keep the contributor informed.
When a PR is created a comment is already created, but the status check can be set, too.
When a Review is done a comment is already created, but the status check can be set, too.
When the Pull Request is updated (due to a push / force push), a comment should be written that the time to merge is reset and the status check can be set accordingly.
This will make sure that the information on the Pull Request is more up to date and contributors are better informed about the current status.
...
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 locating the GitHub webhook handlers for pull request creation, review completion, and pull request updates. Trace how comments are currently created and how commit statuses are set for each event. Done means each listed event updates the status appropriately and provides the requested contributor-facing comment, including the merge-time reset after pushes or force pushes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100