Support Signed Commits by actions@github.com
See original GitHub issueCurrently if “signed commits” are required in branch protection there is no good way to have actions update code using the token provided for use with github actions and the current repository. Seems like github actions should provide a way for changes made by actions@github.com
to be signed and show as verified through the interface.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:240
- Comments:24
Top Results From Across the Web
Sign automatic commits in GitHub Actions
Git and GitHub API in Python. This repo contains some examples and an article about how to sign commits automatically using GitHub Actions....
Read more >Keyless Git commit signing with Gitsign and GitHub Actions
Git commit signing has historically been done with GPG keys, with recent support being added for SSH and x509 certs. However, managing and ......
Read more >Commit signing support for bots and other GitHub Apps
Commit signing allows a user (or bot) to cryptographically vouch for the integrity of the commit, and that they authored it. If a...
Read more >Enable Gitsign Today and Start Signing your Commits
Gitsign supports verifying your identity either through GitHub, ... Setting up Gitsign to start signing your commits is a two-step process: ...
Read more >Change display name for GitHub Actions Bot commit
Use a different emailaddress and you can choose the name to display and as long as the email is unknown to Microsoft Github,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Is there any traction at all from github? This is crucial for us as signed commits have been made mandatory for our repositories and creating and managing non-human accounts is not really trivial. In my eyes signed commits need to be supported by github actions directly rather than us having to jump through hoops.
What’s the cryptographic purpose for this? If any action can create signed commits under
actions@github.com
, then what does the signature indicate, that the commit was made on GitHub Actions rather than on humans’ local machine?The actual feature we should propose is to recognize
myname+actions@github.com
as a non-human account associated with me, and can be verified by my GPG keys. All I need is to store a private key as actions secret and use it for signing the commits.