From dba899cbeb4903c39095158ab33a9ec852e44de6 Mon Sep 17 00:00:00 2001 From: Lukas Klingsbo Date: Mon, 8 Jun 2026 11:11:18 +0200 Subject: [PATCH 1/2] docs: Update commit message examples in CONTRIBUTING.md Clarified commit message format examples in CONTRIBUTING.md. --- CONTRIBUTING.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 9951262..126f6b2 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -32,7 +32,8 @@ 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 @@ -40,4 +41,4 @@ Before creating pull requests for new features, first file a GitHub Issue descri ## License -By contributing to Supabase, you agree that your contributions will be licensed under its license specified in the repository you are contributing to. \ No newline at end of file +By contributing to Supabase, you agree that your contributions will be licensed under its license specified in the repository you are contributing to. From 54857d61c71e4d84288fff79dd6aaaf1b1cb6c11 Mon Sep 17 00:00:00 2001 From: Lukas Klingsbo Date: Mon, 8 Jun 2026 11:13:49 +0200 Subject: [PATCH 2/2] Apply suggestion from @spydon --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 126f6b2..722bf34 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -33,7 +33,7 @@ When making pull requests to the repository, make sure to follow these guideline - 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 breaking changes, remember to include an exclamation mark after the tag, for example: `feat(extension-name)!: changed endpoint format` + - For breaking changes, remember to include an exclamation mark after the tag, for example: `feat(extension-name)!: changed endpoint format`. ### Features