29 lines
937 B
Markdown
29 lines
937 B
Markdown
# 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-all` passes (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
|
|
- [x] 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)
|