Skip to content

Commit d39e4e8

Browse files
authored
docs: document signed commit requirement (#406)
Add the Grafana Labs signed-commit requirement to the contributor documentation.\n\nThis mirrors grafana/docker-otel-lgtm#1599.\n\nDocumentation-only change; no tests are required. Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
1 parent 02dbe56 commit d39e4e8

1 file changed

Lines changed: 13 additions & 0 deletions

File tree

CONTRIBUTING.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -34,3 +34,16 @@ Flint branch in a consumer repo, pin a cargo git dependency in that repo's
3434
```
3535

3636
Replace `<git-ref>` with the branch, tag, or commit you want to test.
37+
38+
## Submit a pull request
39+
40+
Effective 2026-06-22, all Grafana Labs repositories [require signed commits][signed-commits].
41+
To learn more about Git commit verification, refer to [About commit signature verification][signing-commits]
42+
and [Checking your commit signature verification status][verifying-commits].
43+
44+
> [!NOTE]
45+
> Pull requests containing any unsigned commits cannot be merged until all commits are signed.
46+
47+
[signed-commits]: https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches#require-signed-commits
48+
[signing-commits]: https://docs.github.com/authentication/managing-commit-signature-verification/about-commit-signature-verification
49+
[verifying-commits]: https://docs.github.com/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status

0 commit comments

Comments
 (0)