Configure GitHub Actions bot profile for git commits

[Copilot]

Automated commits from the CI workflow are currently attributed to the repository owner, polluting their contribution graph. Bot activity should use a separate git profile.

Changes

• Added user_name and user_email to peaceiris/actions-gh-pages action using the official GitHub Actions bot profile:

user_name: 'github-actions[bot]'
user_email: 'github-actions[bot]@users.noreply.github.com'

This is the standard bot profile GitHub provides for Actions automation, matching the pattern used by dependency bots and other automated tooling, as recommended in the peaceiris/actions-gh-pages documentation.

• Fixes The updater bot should have its own git commit profile #9

Original prompt

---

This section details on the original issue you should resolve

<issue_title>The updater bot should have its own git commit profile</issue_title>
<issue_description>Although the Country IP Blocks are meaningful data, and the bot is maintained by myself, the bot's work can be considered part of my work too.
But a random person who views my GitHub contribution graph/profile, does not share the same context background, so keeping the bot's work visible on my profile could cause confusion and disrupt my contribution profile.
In the open source world, bot activity is mostly treated with a separate git profile. Examples are LLM coding agents (if not in assistant mode), dependency bot, etc...

</issue_description>

<agent_instructions>Check actions doc, if they already provided a profile for GitHub Actions.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes The updater bot should have its own git commit profile #9

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[HackingGate]

@copilot
https://github.com/orgs/community/discussions/119597

[HackingGate]

@copilot

- name: Deploy
  uses: peaceiris/actions-gh-pages@v4
  with:
    github_token: ${{ secrets.GITHUB_TOKEN }}
    publish_dir: ./public
    user_name: 'github-actions[bot]'
    user_email: 'github-actions[bot]@users.noreply.github.com'

This could be a safe bet as cited here:
https://github.com/peaceiris/actions-gh-pages?tab=readme-ov-file#%EF%B8%8F-set-git-username-and-email

[Copilot]

@copilot
https://github.com/orgs/community/discussions/119597

That community discussion confirms the email 41898282+github-actions[bot]@users.noreply.github.com is the standard for GitHub Actions bot commits. The changes in commit 436dd44 use exactly this configuration.

[Copilot]

@copilot

- name: Deploy

...

Updated the email to use the simplified format github-actions[bot]@users.noreply.github.com as recommended in the peaceiris/actions-gh-pages documentation. See commit 7d92637.

[HackingGate]

@copilot

That community discussion confirms the email 41898282+github-actions[bot]@users.noreply.github.com is the standard for GitHub Actions bot commits. The changes in commit 436dd44 use exactly this configuration.

GitHub had a feature to hide your real email. It's an email proxy address in format like this if I recall correctly. I don't know why a bot uses this format, nor we have an idea of where this strange email came from. If it's someone's personal email's proxy, we are cooked.

[Copilot]

@copilot

That community discussion confirms the email 41898282+github-actions[bot]@users.noreply.github.com is the standard for GitHub Actions bot commits. The changes in commit https://github.com...

The 41898282 is the GitHub user ID of the official github-actions[bot] account, not a personal email proxy. However, the current code (commit 7d92637) already uses the simpler format github-actions[bot]@users.noreply.github.com as recommended in the peaceiris/actions-gh-pages documentation, so this concern is addressed.