-
Notifications
You must be signed in to change notification settings - Fork 200
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(docs): Introduce Conventional Commits & release process docs #717
Conversation
@critesjosh and or @Globallager can you take a look at the now SUPPORT.MD file? |
Added them as reviewers, but worth noting that I just copy-pasted from CONTRIBUTING.md so we didn't lose anything. |
Should we also disable normal & rebase PR merges to better enforce squash merging once this goes in? cc @kevaundray |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm happy with this plan.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me
4dc28a1
4dc28a1
to
686fbb5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
* master: feat(nargo): Add `nargo test` command to run all unit tests (noir-lang#728) chore(ci): Apply `doc needed` label automatically on PRs (noir-lang#733) chore(ci): Remove failing bors workflow (noir-lang#744) feat(ci): Add workflow to validate PR title (noir-lang#730) feat(docs): Introduce Conventional Commits & release process docs (noir-lang#717)
Related issue(s)
Resolves #607
Description
This introduces a process for Noir releases that leverages Conventional Commits and the release-please tool to produce a "release pull request" containing an auto-generated changelog, appropriate SemVer bumps, and lockfile updates.
Summary of changes
I reorganized the
SUPPORT.md
file to contain community-facing things, and then updatedCONTRIBUTING.md
to discuss my proposed release solution. I also updated therelease.yml
workflow to use release-please.Dependency additions / changes
Test additions / changes
Checklist
cargo fmt
with default settings.Additional context
I'll be discussing our workflow changes at the scheduled meeting time 🎉
We'll also want to tag a version right before we land this so we can have everything onward follow the convention.