Skip to content
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

Merged
merged 6 commits into from
Feb 3, 2023

Conversation

phated
Copy link
Contributor

@phated phated commented Jan 31, 2023

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 updated CONTRIBUTING.md to discuss my proposed release solution. I also updated the release.yml workflow to use release-please.

Dependency additions / changes

Test additions / changes

Checklist

  • I have tested the changes locally.
  • I have formatted the changes with Prettier and/or cargo fmt with default settings.
  • I have linked this PR to the issue(s) that it resolves.
  • I have reviewed the changes on GitHub, line by line.
  • I have ensured all changes are covered in the description.

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.

@kevaundray
Copy link
Contributor

@critesjosh and or @Globallager can you take a look at the now SUPPORT.MD file?

@phated
Copy link
Contributor Author

phated commented Jan 31, 2023

Added them as reviewers, but worth noting that I just copy-pasted from CONTRIBUTING.md so we didn't lose anything.

Savio-Sou
Savio-Sou previously approved these changes Feb 1, 2023
@Savio-Sou
Copy link
Collaborator

Should we also disable normal & rebase PR merges to better enforce squash merging once this goes in? cc @kevaundray

image

TomAFrench
TomAFrench previously approved these changes Feb 1, 2023
Copy link
Member

@TomAFrench TomAFrench left a 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.

CONTRIBUTING.md Outdated Show resolved Hide resolved
vezenovm
vezenovm previously approved these changes Feb 1, 2023
Copy link
Contributor

@vezenovm vezenovm left a 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

kevaundray
kevaundray previously approved these changes Feb 3, 2023
Copy link
Contributor

@kevaundray kevaundray left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@phated phated changed the title feat(docs)!: Introduce Conventional Commits & release process docs feat(docs): Introduce Conventional Commits & release process docs Feb 3, 2023
@phated phated merged commit 950ca55 into master Feb 3, 2023
@phated phated deleted the phated/release-process branch February 3, 2023 20:17
TomAFrench added a commit to TomAFrench/noir that referenced this pull request Feb 3, 2023
* 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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Display correct software version
7 participants