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.

Sign up for GitHub

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

chore: add Conventional Commits ref to the contribution guide #1303

Merged
merged 1 commit into from
Apr 18, 2024
Merged

chore: add Conventional Commits ref to the contribution guide #1303

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -194,7 +194,10 @@ to your valuable work:
[here](https://medium.com/@slamflipstrom/a-beginners-guide-to-squashing-commits-with-git-rebase-8185cf6e62ec), and if you're
having trouble - feel free to ask a member or the community for help or leave the commits as-is, and flag that you'd like
rebasing assistance in your PR! We're here to support you.
- Open a PR in the project to bring in the code from your feature branch.
- Open a PR in the project to bring in the code from your feature branch. We use
[Conventional Commits](https://www.conventionalcommits.org/), so prefix your PR title
with `feat:`, `fix:`, or `chore:` appropriately. `feat` will result in a minor version
bump, and `fix` will result in a patch version bump.
- The maintainers noted in the `CODEOWNERS` file will review your PR and optionally
open a discussion about its contents before moving forward.
- Remain responsive to follow-up questions, be open to making requested changes, and...
Expand Down