From c85cb2d37fee6e0467f530c6910775c57dbccf0e Mon Sep 17 00:00:00 2001 From: Igor Racic Date: Thu, 12 Feb 2026 13:53:38 +0100 Subject: [PATCH] docs: document DCO enforcement policy and conventional commits - Add note that DCO enforcement is active since v0.6.0 - Update commit message guidelines to conventional commits format - Align examples with actual project conventions Signed-off-by: Igor Racic --- CONTRIBUTING.md | 20 +++++++++++++------- 1 file changed, 13 insertions(+), 7 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 05b12a4..63c4345 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -110,12 +110,16 @@ mypy src/dns_aid ### Commit Message Guidelines -Use clear, descriptive commit messages: -- `Add: new feature description` -- `Fix: bug description` -- `Update: what was changed` -- `Remove: what was removed` -- `Refactor: what was refactored` +We follow [Conventional Commits](https://www.conventionalcommits.org/): + +``` +feat: add DANE certificate matching support +fix: Route53 SVCB custom param demotion to TXT records +chore: bump version to 0.6.0 +docs: update architecture diagram +``` + +All commits **must** include a DCO sign-off (see below). ## Pull Request Guidelines @@ -149,11 +153,13 @@ This project uses the [Developer Certificate of Origin](https://developercertifi By submitting a patch, you agree to the DCO. All commits must include a `Signed-off-by` line: ```bash -git commit -s -m "Your commit message" +git commit -s -m "feat: your commit message" ``` This certifies that you wrote or have the right to submit the code under the project's open-source license. +> **Note:** DCO sign-off enforcement has been active since v0.6.0. All pull requests are automatically checked by the DCO workflow, and branch protection requires it to pass before merging. + ## License By contributing, you agree that your contributions will be licensed under the Apache 2.0 License.