Skip to content

docs: Update commit message examples in CONTRIBUTING.md #18

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

Open
spydon wants to merge 2 commits into
base: main
Choose a base branch
from
+3 −2
Open

docs: Update commit message examples in CONTRIBUTING.md #18

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
dba899c
docs: Update commit message examples in CONTRIBUTING.md
spydon Jun 8, 2026
54857d6
Apply suggestion from @spydon
spydon Jun 8, 2026
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: 3 additions & 2 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,12 +32,13 @@ When making pull requests to the repository, make sure to follow these guideline
- Before creating a pull request, file a GitHub Issue so that maintainers and the community can discuss the problem and potential solutions before you spend time on an implementation.
- In your PR's description, link to any related issues or pull requests to give reviewers the full context of your change.
- For commit messages, follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) format.
- For example, if you update documentation for a specific extension, your commit message might be: `docs(extension-name) updated installation documentation`.
- For example, if you update documentation for a specific extension, your commit message might be: `docs(extension-name): updated installation documentation`.
- For breaking changes, remember to include an exclamation mark after the tag, for example: `feat(extension-name)!: changed endpoint format`.

### Features

Before creating pull requests for new features, first file a GitHub Issue describing the reasoning and motivation for the feature. This gives maintainers and the community the opportunity to provide feedback on your idea before implementing it.

## License

By contributing to Supabase, you agree that your contributions will be licensed under its license specified in the repository you are contributing to.
By contributing to Supabase, you agree that your contributions will be licensed under its license specified in the repository you are contributing to.