You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Enable a merge queue on main so PRs merge through a validated queue rather than directly.
Status
✅ Workflow half is done. The Go workflow now runs on the merge_group event (PR ci: run on merge_group so a merge queue can gate PRs #110, merged to main), so its build check will execute against the queue's candidate merge commits.
⛔ Repo-setting half is blocked. Creating the ruleset that turns the queue on requires the Administration: Read and write permission, which the current automation token lacks — POST /repos/argonui/TTSModManager/rulesets returns 403 Resource not accessible by personal access token.
What needs to happen
Someone with admin access finishes this one of two ways.
Option A — grant the token Administration: Read and write, then the ruleset can be created via API. Ready-to-use payload:
Task
Enable a merge queue on
mainso PRs merge through a validated queue rather than directly.Status
merge_groupevent (PR ci: run on merge_group so a merge queue can gate PRs #110, merged tomain), so itsbuildcheck will execute against the queue's candidate merge commits.POST /repos/argonui/TTSModManager/rulesetsreturns403 Resource not accessible by personal access token.What needs to happen
Someone with admin access finishes this one of two ways.
Option A — grant the token Administration: Read and write, then the ruleset can be created via API. Ready-to-use payload:
{ "name": "main merge queue", "target": "branch", "enforcement": "active", "conditions": { "ref_name": { "include": ["~DEFAULT_BRANCH"], "exclude": [] } }, "rules": [ { "type": "merge_queue", "parameters": { "merge_method": "MERGE", "grouping_strategy": "ALLGREEN", "max_entries_to_build": 5, "max_entries_to_merge": 5, "min_entries_to_merge": 1, "min_entries_to_merge_wait_minutes": 5, "check_response_timeout_minutes": 60 } }, { "type": "required_status_checks", "parameters": { "required_status_checks": [ { "context": "build" } ], "strict_required_status_checks_policy": false, "do_not_enforce_on_create": false } } ] }Option B — configure it in the UI: Settings → Rules → Rulesets → New branch ruleset:
build.Notes
merge_groupis already onmain, the queue's requiredbuildcheck can run. (Enabling it before PR ci: run on merge_group so a merge queue can gate PRs #110 landed would have deadlocked merges.)build) and merge-commit method.