This is carried over from #1184. Below is the original PR body. This PR updates the base for actions/checkout@v4

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:

• actions/toolkit/.github/workflows/update-github.yam uses github-actions[bot] + [email protected] which does not give a proper avatar on the commit
• actions/deploy-pages/.github/workflows/rebuild-dependabot-prs.yml uses the setup suggested in this PR (github-actions[bot] + github-actions[bot]@users.noreply.github.com) apart from lacking the 41898282+ prefix to the email
• actions/runner-images/.github/workflows/merge_pull_request.yml uses Actions service account + [email protected]
• actions/actions-runner-controller/.github/workflows/update-runners.yaml uses uses the exact same setup as suggested here, referencing this discussion as the source of why that is correct

(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