This repository has been archived by the owner on Apr 12, 2019. It is now read-only.
Add parsing support for tag GPG signatures #124
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## master #124 +/- ##
==========================================
+ Coverage 32.78% 33.54% +0.76%
==========================================
Files 25 25
Lines 1397 1407 +10
==========================================
+ Hits 458 472 +14
+ Misses 868 862 -6
- Partials 71 73 +2
Continue to review full report at Codecov.
|
lafriks
approved these changes
Jul 8, 2018
|
LGTM |
7 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In trying to solve go-gitea/gitea#4137, I realized that tag signatures lack the "gpgsig" prefix that commit signatures have. Instead it is put after the commit message. So I attempted to add support for this in the "parseCommitData" function.