doc: Release / contribution guide updates#195
Open
hcallahan-lowrisc wants to merge 3 commits into
Open
Conversation
hcallahan-lowrisc
force-pushed
the
release_contrib_updates
branch
from
962511b to
b9a99ee
Compare
Signed-off-by: Harry Callahan <hcallahan@lowrisc.org>
- Summarize important contribution guidelines in checklist - Describe the commit message format for automatic semver releases Signed-off-by: Harry Callahan <hcallahan@lowrisc.org>
- Remove obsolete style guidance that was more opentitan specific - Conventional Commit / SemVer impact guidelines for commit message - Minor style and prose cleanups and simplifications Signed-off-by: Harry Callahan <hcallahan@lowrisc.org>
hcallahan-lowrisc
force-pushed
the
release_contrib_updates
branch
from
b9a99ee to
e246568
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Flesh out the contribution guidelines and docs to better reflect the use of conventional commits / semantic-release to automate project releases, and the expectations upon contributors to follow these guidelines to categorize their contributions appropriately.
releasing.mddocument explaining the conventional commits style and automated release processes.