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

Use full git email for github-actions bot #448

Merged
merged 2 commits into from
Mar 10, 2025
Merged

Conversation

bluwy
Copy link
Contributor

@bluwy bluwy commented Mar 10, 2025

The full git email for github-actions[bot] has the initial 41898282+ part.

Initially I thought fixing this would make GitHub no longer generate co-author descriptions by default, because the PR author and the commit author are already the same bot. Example. But after fixing the email myself and releasing again, the co-author is still there. Example

So while this doesn't quite fix anything, and I could also remove the co-author manually if I wanted, I thought it's still beneficial to update this to be consistent and maybe one day GitHub might fix this.

NOTE: The original full email can be retrieved by prepending .patch to the commit URLs above. Example

Copy link

changeset-bot bot commented Mar 10, 2025

🦋 Changeset detected

Latest commit: 5fac6ae

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@changesets/action Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@@ -9,7 +9,7 @@ export const setupUser = async () => {
await exec("git", [
"config",
"user.email",
`"github-actions[bot]@users.noreply.github.com"`,
`"41898282+github-actions[bot]@users.noreply.github.com"`,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this number stable? 🤔

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess it's its ID... so it should be stable 🤷‍♂️

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I think it should. The earliest mention I found was from 2020, and the checkout action also mentions it. So likely safe enough.

@Andarist Andarist merged commit 8b16070 into changesets:main Mar 10, 2025
1 check passed
@github-actions github-actions bot mentioned this pull request Mar 10, 2025
@bluwy bluwy deleted the patch-1 branch March 10, 2025 10:44
calvinjd pushed a commit to calvinjd/changesets-action that referenced this pull request Mar 10, 2025
* Use full git email for github-actions bot

* Create fluffy-clocks-knock.md
@changesets changesets deleted a comment Mar 20, 2025
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.

2 participants