Skip to content

Parse gpgsig in commits#22

Open
joelpurra wants to merge 1 commit intotarmstrong:masterfrom
joelpurra:parse-gpgsig
Open

Parse gpgsig in commits#22
joelpurra wants to merge 1 commit intotarmstrong:masterfrom
joelpurra:parse-gpgsig

Conversation

@joelpurra
Copy link

@joelpurra joelpurra commented Sep 21, 2021

  • Git commits can optionally be signed using GNU Privacy Guard (GPG).
  • Without checking for gpgsig in the git output, signed commits would be skipped by git2json.
  • Adds the gpgsig property to each commit in the JSON output.
    • Signed commits use the multiline signature string.
    • Unsigned commits use null.
  • The signature is not cryptographically verified by git2json.
  • Note that signed tags may be more common, but this change is only for signed commits.

See

Note: the commit in this pull request (6bf773d) is signed, and can be used for testing.

- Git commits can optionally be signed using GNU Privacy Guard (GPG).
- Without checking for `gpgsig` in the `git` output, signed commits would be skipped by `git2json`.
- Adds the `gpgsig` property to each commit in the JSON output.
  - Signed commits use the multiline signature string.
  - Unsigned commits use `null`.
- The signature is not cryptographically verified by `git2json`.
- Note that signed _tags_ may be more common, but this change is only for signed _commits_.

See

- https://en.wikipedia.org/wiki/GNU_Privacy_Guard
- https://git-scm.com/book/en/v2/Git-Tools-Signing-Your-Work
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant