From a2e0cabc1ba2f76029bc0cf23e96ff097265f9d2 Mon Sep 17 00:00:00 2001 From: Aminda Suomalainen Date: Sun, 9 Jan 2022 21:56:58 +0200 Subject: [PATCH] README.md: cut forge support to its own section --- README.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index a2b7bc4..6aa5aa6 100644 --- a/README.md +++ b/README.md @@ -37,7 +37,12 @@ would understand `--` before the file, but not enough to actually try it :smiley ## Further reading * [Caleb Hearth: Signing Git Commits with Your SSH Key](https://calebhearth.com/sign-git-with-ssh) ([web.archive.org](https://web.archive.org/web/20211117182628/https://calebhearth.com/sign-git-with-ssh)) inspired me to try this -* [GitHub feedback: Allow using SSH keys to sign commits](https://github.com/github/feedback/discussions/7744) - * TODO: notify here when it actually works, link to their guide or maybe remove the section? + +### Forge support + * [Merged Gitea PR for add support for ssh commit signing](https://github.com/go-gitea/gitea/pull/17743) * TODO: link to their blog once it's released +* [GitHub feedback: Allow using SSH keys to sign commits](https://github.com/github/feedback/discussions/7744) + * TODO: notify here when it actually works, link to their guide or maybe remove the section? +* [GitLab issues: Support for SSH signed commits](https://gitlab.com/gitlab-org/gitlab/-/issues/343879) + * TODO: a better link when this happens