suzanne.soy/qubes-doc
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Describe why tags are optional

Browse Source 
- https://github.com/QubesOS/qubes-doc/pull/666#issuecomment-400115131
- fix indentation
  - https://github.com/QubesOS/qubes-doc/pull/666#discussion_r198002571
  - https://github.com/QubesOS/qubes-doc/pull/666#discussion_r198002716
This commit is contained in:
Nicco Kunzmann 2018-06-26 10:24:18 +02:00
parent 090d617e91
commit 5e1731c7ea
No known key found for this signature in database
GPG Key ID: 9BBAB2DEB1488C99
1 changed files with 10 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
basics_dev/code-signing.md
View File

@ -104,7 +104,13 @@ your Git commits.
commit -S
~~~
3. (Optional) Create signed tags:
3. (Optional) Create signed tags.
Signed commits are totally sufficient to contribute to Qubes OS.
However, if you have commits which are not signed and you do not want to change them,
you can create a signed tag for the commit and push it before the check.
This is useful for example, if you have a commit back in the git history which
you like to sign now without rewriting the history.
~~~
git tag -s <tag_name> -m "<tag_message>"
@ -116,15 +122,15 @@ your Git commits.
~~~
[alias]
stag = "!bash -c 'id=\"`git rev-parse --verify HEAD`\"; tag_name="signed_tag_for_${id:0:8}"; git tag -s "$tag_name" -m \"Tag for commit $id\"; echo \"$tag_name\"'"
spush = "!bash -c 'git push origin `git stag`'"
stag = "!bash -c 'id=\"`git rev-parse --verify HEAD`\"; tag_name="signed_tag_for_${id:0:8}"; git tag -s "$tag_name" -m \"Tag for commit $id\"; echo \"$tag_name\"'"
spush = "!bash -c 'git push origin `git stag`'"
~~~
You may also find it convenient to have an alias for verifying the tag on the
latest commit:
~~~
vtag = !git tag -v `git describe`
vtag = !git tag -v `git describe`
~~~
How to Contribute Signed Code