Is your feature request related to a problem? Please describe.
Currently, when I set COMMIT_BY_ME: "False", the commit's Author and Committer are successfully set to readme-bot (or the configured bot name and email). This keeps the bot's commits off my GitHub Contribution Graph, which is great.
However, because the Action uses the personal access token (GH_TOKEN) to authenticate the actual git push operation, GitHub registers the "Push Event" under my personal account. Consequently, my GitHub Activity Feed displays these pushes as my own, and third-party GitHub activity trackers incorrectly count these bot operations as my daily personal activity.
Describe the solution you'd like
I believe a good solution is to separate the token used for fetching data from the token used for pushing code.
Specifically, we could add a configuration option (or a new input like PUSH_TOKEN) that utilizes the automatically generated GitHub Actions token (${{ github.token }}) for the git push authentication.
- The personal
GH_TOKEN (PAT) would still be kept and used to fetch accurate and complete GitHub metrics. (Removing it would break compatibility and data accuracy, so it must stay).
- The Actions
GITHUB_TOKEN would only be used for configuring the git remote URL to push the commit.
This way, the push event is registered by github-actions[bot] entirely, solving the false activity tracking issue.
Describe alternatives you've considered
An alternative is completely ignoring the issue, but for users who care about accurate activity tracking (like not wanting daily automated pushes to flood their personal activity feed), this becomes quite annoying over time.
Additional context
I am opening this issue to ask for your opinion on this approach. If you think this is a valid improvement and agree with the proposed solution, I would be more than happy to work on this and submit a Pull Request.
Is your feature request related to a problem? Please describe.
Currently, when I set
COMMIT_BY_ME: "False", the commit's Author and Committer are successfully set toreadme-bot(or the configured bot name and email). This keeps the bot's commits off my GitHub Contribution Graph, which is great.However, because the Action uses the personal access token (
GH_TOKEN) to authenticate the actualgit pushoperation, GitHub registers the "Push Event" under my personal account. Consequently, my GitHub Activity Feed displays these pushes as my own, and third-party GitHub activity trackers incorrectly count these bot operations as my daily personal activity.Describe the solution you'd like
I believe a good solution is to separate the token used for fetching data from the token used for pushing code.
Specifically, we could add a configuration option (or a new input like
PUSH_TOKEN) that utilizes the automatically generated GitHub Actions token (${{ github.token }}) for thegit pushauthentication.GH_TOKEN(PAT) would still be kept and used to fetch accurate and complete GitHub metrics. (Removing it would break compatibility and data accuracy, so it must stay).GITHUB_TOKENwould only be used for configuring the git remote URL to push the commit.This way, the push event is registered by
github-actions[bot]entirely, solving the false activity tracking issue.Describe alternatives you've considered
An alternative is completely ignoring the issue, but for users who care about accurate activity tracking (like not wanting daily automated pushes to flood their personal activity feed), this becomes quite annoying over time.
Additional context
I am opening this issue to ask for your opinion on this approach. If you think this is a valid improvement and agree with the proposed solution, I would be more than happy to work on this and submit a Pull Request.