[8.14] ci(signed-commits): use GPG signing (backport #13069) #13092
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
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation/summary
Support signed commits using a GPG linked to the user used for the automation.
I double-checked different alternatives as explained in actions/runner#667
But decided to use a native GitHub action for the sake of simplicity; eventually, we could use the GitHub graphql approach, but I don't know if that behaviour will change in the future. For now, I think it's safer to use the default standard approach.
Checklist
For functional changes, consider:
How to test these changes
Related issues
Part of #12995
This is an automatic backport of pull request #13069 done by Mergify.