rosflight / rosflight/rosflight_docs
Add docs for versioning pipeline
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 1
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
On the "Contributing to ROSflight" docs we need to describe our versioning pipeline and how contributors/maintainers should use release-please and what/when changes should be pushed to main.
This is essential for continuity and consistent maintenance as students graduate.
Contributor guide
No contributing guide indexed for this repository
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
Locate the “Contributing to ROSflight” documentation and read the surrounding contributor and maintenance guidance first. Document how the versioning pipeline uses release-please and what contributors and maintainers should push to main, including when; the work is done when this process is clear enough to support consistent releases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100