Skip to content
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

README: Suggest user.email to be 41898282+github-actions[bot]@users.noreply.github.com #1184

Closed
wants to merge 3 commits into from

Conversation

voxpelli
Copy link
Contributor

@voxpelli voxpelli commented Feb 22, 2023

To get a proper GitHub Actions Bot annotation to a commit one should set the user.name and user.email to:

git config user.name "github-actions[bot]"
git config user.email "41898282+github-actions[bot]@users.noreply.github.com"

There are some confusion around this in the actions/ org itself:

(Another interesting aspect of the linked to workflows is that some use --local when setting the name and email, some use --global and some does what is suggested here and use neither of --local and --global)

Of note is also a third approach from the community, where it strives to achieve custom bot users (+ to get around the limitation of workflow created PR:s not running workflows): https://github.com/wow-actions/use-app-token Such a env.BOT_NAME would be quite nice to have built in to use.

An example generated with this setup can be found here: SocketDev/socket-sdk-js@24f0574

Generated with: https://github.com/SocketDev/workflows/blob/24190c5ca3aa54b086ff1666ed4486f6bc1e9ec9/.github/workflows/reusable-sync.yml#L118-L119

EDIT: Swapped the recommendation to include the prefix 41898282+ as I found out that that's the email used when the bot does eg. squash commits and thus its otherwise showing up as being two different users, which looks a bit confusing. See eg: SocketDev/socket-sdk-js@b0948d0

@voxpelli voxpelli requested a review from a team as a code owner February 22, 2023 12:57
To match squash merge user, else showing as two different users, see: SocketDev/socket-sdk-js@b0948d0
@voxpelli voxpelli changed the title README: Suggest user.email to be github-actions[bot]@users.noreply.github.com README: Suggest user.email to be 41898282+github-actions[bot]@users.noreply.github.com Feb 27, 2023
DennisTsar added a commit to opLetter/course-evals that referenced this pull request Apr 4, 2023
jeffwidman added a commit to dependabot/fetch-metadata that referenced this pull request May 1, 2023
jeffwidman added a commit to dependabot/fetch-metadata that referenced this pull request May 2, 2023
jeffwidman added a commit to github/dependabot-action that referenced this pull request May 12, 2023
jeffwidman added a commit to github/dependabot-action that referenced this pull request May 12, 2023
bananarama92 added a commit to bananarama92/MBS that referenced this pull request May 27, 2023
nullcoder added a commit to nullcoder/devcontainer-features that referenced this pull request Jun 1, 2023
Update git user and email per actions/checkout#1184
nscuro added a commit to DependencyTrack/hyades that referenced this pull request Aug 1, 2023
See actions/checkout#1184

Signed-off-by: nscuro <nscuro@protonmail.com>
mehab pushed a commit to DependencyTrack/hyades that referenced this pull request Sep 12, 2023
See actions/checkout#1184

Signed-off-by: nscuro <nscuro@protonmail.com>
Signed-off-by: mehab <meha.bhargava@citi.com>
@andyfeller
Copy link

@voxpelli : just want to thank you for opening this PR as I myself had the same question. I'm working to raise this up with the Actions team as I think it should be considered and merged 👍

@voxpelli
Copy link
Contributor Author

voxpelli commented Feb 5, 2024

Anything I can do to move this forward @cory-miller and others?

@cory-miller
Copy link
Contributor

Hey @voxpelli I've updated your branch with the actions/checkout@v4 changes. I was not able to run the CI against this since the fork was behind. I've opened a PR in #1707 and will get someone else to approve it.

@cory-miller
Copy link
Contributor

I'm going to close this one out now that #1707 is merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants