qjudge-github-workflow-owner

QJudge GitHub Workflow Owner

Quick start

First sync dev：git switch dev && git fetch origin main && git merge --ff-only origin/main。
From dev create a branch:git switch -c codex/<topic>。
Commit:bash .codex/skills/qjudge-github-workflow-owner/scripts/commit-changes.sh "type: message"。
Open PR:bash .codex/skills/qjudge-github-workflow-owner/scripts/create-pr.sh --base dev --title "title"。

✅ branch naming, commit granularity, PR base/head, PR description and label strategy.
✅ release process (dev -> main）。
✅ pre-merge process gate (check whether quality scripts were run).
❌ Does not define import boundaries (leave to qjudge-architecture-owner）。
❌ Does not define Carbon/UI specifications (leave to qjudge-ui-carbon-owner）。
❌ Does not define compose command details (leave to qjudge-env-compose-owner）。

Only allow:codex/* -> dev or dev -> main。
Do not commit directly on main .
PRs should be small and reviewable: recommended <= 20 files, <= 400 lines added/deleted (special cases require justification in the PR description).
Before opening a PR, at minimum run:
- node .codex/skills/qjudge-quality-gates-owner/scripts/lint-naming.js --root frontend/src
- node .codex/skills/qjudge-quality-gates-owner/scripts/lint-architecture.js --root frontend/src

For matters involving layer responsibilities or path ownership, switch first to qjudge-architecture-owner。
For matters involving UI/Storybook/overflow, switch to qjudge-ui-carbon-owner。
For matters involving container commands or migrate/test execution, switch to qjudge-env-compose-owner。

Portability principle: keep feature branch -> integration branch -> release branch three-stage flow.
If it is not a QJudge project, replace the base branch name and lint command to reuse it.