From 7062e002f8b136df05764c746353ec6045ece2f4 Mon Sep 17 00:00:00 2001 From: Aminda Suomalainen Date: Sat, 5 Feb 2022 17:44:39 +0200 Subject: [PATCH] README.md: reword Gitea support, link to release blogpost --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 8148cdc..46046a9 100644 --- a/README.md +++ b/README.md @@ -42,7 +42,7 @@ would understand `--` before the file, but not enough to actually try it :smiley ### Forge support -* 🥇 [Gitea v1.16.0 released 2022-01-30 (release notes)](https://github.com/go-gitea/gitea/releases/tag/v1.16.0) brought support for SSH signed commits. TODO: Add a link to their blog somewhere on this line once one exists. +* 🥇 [Gitea v1.16.0 brought support for SSH signed commits on 2022-01-30.](https://blog.gitea.io/2022/02/gitea-1.16.0-and-1.16.1-released/) ([tag](https://github.com/go-gitea/gitea/releases/tag/v1.16.0)) * [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)