Skip to content

ci(release): attribute homebrew formula commits to mvwebmaster#245

Merged
mfauzaan merged 2 commits into
mainfrom
fauzaan/release-workflow-committer
May 18, 2026
Merged

ci(release): attribute homebrew formula commits to mvwebmaster#245
mfauzaan merged 2 commits into
mainfrom
fauzaan/release-workflow-committer

Conversation

@mfauzaan

@mfauzaan mfauzaan commented May 18, 2026

Copy link
Copy Markdown
Member

Summary

  • The Homebrew formula bump step in .github/workflows/release.yml hardcoded git config user.name/email to Gan Jun Kai's personal identity, so every release commit pushed to mindvalley/homebrew-wukong was attributed to jk-gan on GitHub.
  • Switch the committer name to the mvwebmaster bot and read the email from a GH_EMAIL GitHub Actions repository variable so it can be rotated without code changes.

Required action before next release

Set the GH_EMAIL repository variable under Settings → Secrets and variables → Actions → Variables (e.g. <USER_ID>+mvwebmaster@users.noreply.github.com for proper GitHub UI attribution). If the variable is empty, the commit will be made with an empty email and may fail commit signing / push rules.

Test plan

  • GH_EMAIL variable set on the repo
  • Next release run pushes a commit to mindvalley/homebrew-wukong authored by mvwebmaster with the configured email

🤖 Generated with Claude Code

mfauzaan and others added 2 commits May 18, 2026 04:32
The Homebrew formula bump pushed by the release workflow is currently
attributed to Gan Jun Kai's personal identity. Switch the committer
identity to the mvwebmaster bot so the push account and the commit
author match.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
So the bot email can be rotated without code changes. Set the
`GH_EMAIL` repository variable in GitHub Actions settings before
the next release run.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@mfauzaan mfauzaan merged commit 6d4214e into main May 18, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants