You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@devlake.apache.org by ab...@apache.org on 2023/01/12 07:32:42 UTC
[incubator-devlake-website] 02/02: docs: update release sop doc and add create a gpg key
This is an automated email from the ASF dual-hosted git repository.
abeizn pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-devlake-website.git
commit fa480260712e455d00a5918ae495c2a535e5bf92
Author: abeizn <zi...@merico.dev>
AuthorDate: Thu Jan 12 15:18:37 2023 +0800
docs: update release sop doc and add create a gpg key
---
docs/DeveloperManuals/Release-SOP.md | 12 +++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/docs/DeveloperManuals/Release-SOP.md b/docs/DeveloperManuals/Release-SOP.md
index ff6fe6ebff..ac63b62b4b 100644
--- a/docs/DeveloperManuals/Release-SOP.md
+++ b/docs/DeveloperManuals/Release-SOP.md
@@ -10,14 +10,20 @@
```
2. Append your public key to the KEYS file
cd devlake
- - Judging that your key is already in the file
+
+ - Check if your public key is in the KEYS file
+ - If it does not, create a new [GPG key](https://docs.github.com/en/authentication/managing-commit-signature-verification/generating-a-new-gpg-key), and then run the following command to see if it was successful.
+
```shell
- gpg --list-sigs <your name>
+ gpg --list-sigs <your name>
```
- - If not, append your publick key
+
+ - Append your publick key
+
```shell
gpg --armor --export <your name> >> KEYS
```
+
3. Upload
```shell
svn add KEYS