Github standard Fork and Pull Request Workflow
Open
Nobody has claimed this yet.
actions
best-practice
github
- Dominant language
- No language data
- Stars
- 17
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
A pretty clear description of the Github workflow we are using, including (command line) steps:
https://gist.github.com/Chaser324/ce0505fbed06b947d962
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 workflow described in the linked Gist and compare it with the repository's current contributor guidance, if any. Clarify where this workflow should be documented; completion would be an accessible, repository-appropriate description of the GitHub fork-and-pull-request steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100