fix(ci): create changelog PR as hoangsvit and approve with eplus-bot#60
Conversation
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
|
Thank you for creating this pull request and helping make the project better. We will review / merge it when we are online. |
|
|
Overall Grade |
Security Reliability Complexity Hygiene |
Code Review Summary
| Analyzer | Status | Updated (UTC) | Details |
|---|---|---|---|
| JavaScript | Jul 15, 2026 12:32a.m. | Review ↗ |
Important
AI Review is run only on demand for your team. We're only showing results of static analysis review right now. To trigger AI Review, comment @deepsourcebot review on this thread.
eplus-bot
left a comment
There was a problem hiding this comment.
Approved by @eplus-bot after all pull request checks passed.
CI run: https://github.com/ePlus-DEV/gmail-alias-toolkit/actions/runs/29379322220
|
Approved by @eplus-bot after all pull request checks passed. Approval refresh: #1 CI run: https://github.com/ePlus-DEV/gmail-alias-toolkit/actions/runs/29379322220 |
|
Thanks for helping make Gmail Alias Toolkit better! |
Summary
Update the release workflow to use two real GitHub accounts with separate responsibilities:
hoangsvitcreates the changelog branch and pull request.eplus-botapproves the pull request after CI passes throughpr-auto-approve.yml.hoangsvitperforms the squash merge after the approval is present.Changes
HOANGSVIT_TOKENas thehoangsvitaccount.EPLUS_BOT_TOKENas theeplus-botaccount.HOANGSVIT_TOKEN.github-actions[bot]from the release workflow.eplus-botapproval tied to the current PR head SHA.HOANGSVIT_TOKEN.Required secret
Add repository Actions secret
HOANGSVIT_TOKENwith a token owned byhoangsvitand sufficient repository contents/pull-request permissions.