Add docs for versioning pipeline

Open Beginner friendly
#73 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Tech stack
git

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.

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.

Dominant language
TeX
Stars
1
Forks
3
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rosflight/rosflight_docs

All issues in rosflight/rosflight_docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.