Provide context to dispatched PRs
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 24
- Forks
- 11
- Avg merge
- 13h 22m
- Merged PRs (30d)
- 15
Description
When something like https://github.com/nextcloud/nextcloud-sharing/pull/2 pops up in my notifications it always takes me a few moments to figure out what a change does, why we need it and what I have to test or pay attention to.
I think we can do better than this. Maybe draw some inspiration from Dependabot.
Would the automation be able to derive that from the information in git?
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 reviewing the example pull request in the issue and comparing its available Git information with the context Dependabot provides. Determine what context should be derived and displayed for dispatched pull requests, then define a way to verify that the generated context explains the change, motivation, and testing considerations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- 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