[New Best Practice Guide]: Versioning Guide
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 36
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
Checked for duplicates
Yes - I've already checked
Describe the needs
We need a guide to port and include in-depth content from https://nasa-ammos.github.io/slim/docs/guides/governance/contributions/pull-requests/#versioning as well as other information about conventional commits and automation tools that can take advantage of that standard (i.e. release-please semantic-release etc.)
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 referenced NASA AMMOS SLIM versioning section and inspect this repository’s existing documentation and governance guides for placement and style. Done means a guide includes the relevant versioning material, explains conventional commits, and covers automation tools such as release-please and semantic-release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100