oblachno-oss/grm
3
0
Fork 0
Code Issues 33 Pull Requests Actions Packages Projects Releases 23 Wiki Activity
Files
7dfdee8b31734af7236c140ed319aaf22a3aabcf
grm/docs/specs/GRM-171-kireto-token-historical.md
T
kireto fe684bad50
Post-merge / detect-and-configure (push) Successful in 50s
Details
Post-merge / release-and-maintain (push) Successful in 3m6s
Details
GRM-171: docs: add runner-ops, molecule-testing, vikunja-tasks skills, fix create-task docs
2026-09-18 22:48:26 +00:00

937 B
Raw Blame History

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

  • 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)
Reference in New Issue View Git Blame Copy Permalink