bluerobotics / bluerobotics/software-guidelines
Version Control: improve "how" and document "why"
Open
- Dominant language
- No language data
- Stars
- 12
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Some relevant discussion/thoughts in [this PR](https://github.com/bluerobotics/cockpit/pull/641).
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the discussion in PR #641, which is the only implementation context provided by the issue. Use that discussion to determine the intended improvements to the version-control guidance, then document both how the project should use version control and why those practices matter.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100