emil
833792d0ad
Post-merge / detect-type (push) Successful in 55s
Post-merge / release (push) Successful in 1m16s
Post-merge / validate-commit-msg (push) Successful in 1m18s
Post-merge / publish (push) Has been skipped
Post-merge / badges (push) Successful in 1m31s
Post-merge / vikunja (push) Successful in 1m20s
Post-merge / configure-repo (push) Successful in 1m18s
Post-merge / sync-wiki (push) Successful in 2m13s
1.7 KiB
1.7 KiB
devx-workflow
Quick reference for devx tools when working on this repo.
PR Workflow (use these, not raw git/tea/MCP)
| Task | Command |
|---|---|
| Create Vikunja task | make create-task -- --title "..." --description "..." |
| Create PR | make create-pr |
| Push + create PR | make push-with-pr |
| Check CI status | make devx-pr-status or make devx-pr-status PR=42 WAIT=1 |
| Fetch CI failure logs | make devx-pr-logs or make devx-pr-logs PR=42 JOB=quality TAIL=50 |
| Add ready-to-merge label | make devx-pr-label or make devx-pr-label PR=42 |
| Post PR review | make devx-pr-review PR=42 EVENT=APPROVE BODY="..." CHECKLIST=1,2,3,4,5,6,7,8,9,10,11,12,13 |
| Rebase current branch | make rebase |
| Rebase PR via API | make pr-rebase or make pr-rebase PR=42 |
Auto-merge Behavior
When the ready-to-merge label is added and all CI checks pass:
- Auto-merge validates PR title format (
GRM-N: <vikunja task title>) - If branch is behind master, auto-merge rebases via Gitea API automatically
- The rebase triggers a new CI run; the next auto-merge attempt merges
- No manual rebase needed unless the API rebase fails
Pre-merge Check
CI runs a pre-merge-check job early (after quality + detect-changes)
that validates branch format, PR title, and Vikunja task match.
This fails fast before expensive molecule tests run.
Key Rules
- Never manually merge via API — always use auto-merge with
ready-to-mergelabel - Branch naming:
GRM-N-short-description(N = Vikunja task ID) - Commit format: conventional commits (
feat:,fix:,docs:, etc.) - PR title:
GRM-N: <vikunja task title>(auto-derived bymake create-pr)