dblock / dblock/code.dblock.org
Document my typical git workflow
Open
Nobody has claimed this yet.
new feature
- Dominant language
- JavaScript
- Stars
- 7
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
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 with the linked log4jna pull-request comment as the example of the desired workflow documentation. Identify this repository's documentation entry point, then record the typical Git workflow there; done when the workflow is documented clearly and the resulting documentation is readable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100