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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Commit signing backend implementation #3007
Commit signing backend implementation #3007
Changes from 1 commit
c1269be
26debc4
9e83c2c
f5081d1
2e7bd0c
5c752c6
b5f4576
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@necauqua maybe the default should be "gpg"?
(just spotted because the test uses "gpg" not "gpg2")
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the gpg2 command is the one that requires the agent to work?.
(and also gpg 2.x)
So that agent use is enforced since we sign every snapshot and whatnot
Anyway I don't remember there being any other reasons, so could be gpg, yes, maybe I forgot to get back to think about this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps, it's historical thing? I don't have
gpg2
in my Debian unstable environment, andgpg --version
says it's 2.x.https://packages.debian.org/bookworm/gnupg2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You don't?.
I thought it was a symlink that every gpg 2.x also installs or something
I have it on NixOS
Yes it is a historical thing afaiu
Anyway I've no objections to changing the default to just gpg
Any unusual or historical setups could change the config value anyway
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@yuja but then here we'd also need to not forget to add
--keyid-format=long
which is the default in gpg2(I just noticed that reading a commit message where they added that very argument to gpg call in git; I think I have it in my personal gpg config set to be the default too)