feat: allow using graphql API to get signed commits #459
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.
Potentially closes #427
Adds
apiProtocolinput that can be set to eitherrest(default) orgraphqlto use GitHub's graphql API to make the commit for the release PR. When used in combination with settingsetupGitUsertofalsethe commit will use the user of the providedGITHUB_TOKEN.This solves an issue we have at my company where the security team wants us to enforce signed commits on all of our repositories. With this change, the commits are signed with the service account user associated with the
GITHUB_TOKEN.Related change is #391 . However we can't use this approach at my company, as the security team wants us to only use our service account, and to not use GPG keys.