Emil SimeonovandDevin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
e4fa2034bd
CI / validate (pull_request) Successful in 1m35s
CI / molecule-tests (1) (pull_request) Skipped
CI / molecule-tests (2) (pull_request) Skipped
CI / molecule-tests (3) (pull_request) Skipped
CI / molecule-tests (4) (pull_request) Skipped
CI / auto-merge (pull_request) Successful in 1m6s
REVIEWER_GITEA_API_TOKEN (emil) is the same user that creates PRs, so Gitea ignores the self-approval. Switch to DEVELOPER_GITEA_API_TOKEN (kireto) — a different user — so the approval counts toward branch protection. Generated with [Devin](https://devin.ai) Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
937 B
937 B
GRM-171: Use kireto token for auto-merge approval review
Problem
The auto-merge workflow posts approval reviews with
REVIEWER_GITEA_API_TOKEN (emil), but emil is also the PR creator.
Gitea ignores self-approvals, so the merge fails with HTTP 405
Does not have enough approvals.
Approach
REQ-1: Change the approval review step in .gitea/workflows/ci.yml to use
DEVELOPER_GITEA_API_TOKEN (kireto) instead of
REVIEWER_GITEA_API_TOKEN (emil), since kireto is a different user
than the PR creator.
Test Plan
make lint-allpasses (workflow-lint validates the YAML)- Next auto-merge PR succeeds (approval posted by kireto, merge completes)
Deploy Plan
- Merge to master
Rollback Plan
- Revert the merge commit
Acceptance Criteria
- REQ-1: Change the approval review step in
.gitea/workflows/ci.ymlto useDEVELOPER_GITEA_API_TOKEN(kireto) instead ofREVIEWER_GITEA_API_TOKEN(emil)