plugins/git
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix/skill-check-compliance-and-flow #21

Merged
admin merged 6 commits from fix/skill-check-compliance-and-flow into develop 2026-08-31 03:24:26 +00:00
Conversation 1 Commits 6 Files Changed 9
+3 -3
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit 113b044bb6 - Show all commits
skills/pr/SKILL.md
+3 -3
View File
@@ -41,7 +41,7 @@ The ladder rules live in one place only: section 「PR 分支階梯」 of `jsc-m
- Exit 4 (API call failed) → stop and report the failure. Never read a failed call as "no open PR": that opens a second PR on a branch that already has one.
- Any other non-zero → treat it as exit 4 and stop.
- Done when either the PR number plus its title, base and body are held, or exit 3 confirmed the branch has no open PR.
7. Create the PR, then hang its prerequisite on it. Run `jsc-gitea/tools/gitea.sh pr-create {owner}/{repo} {target branch} {base branch} "{branch name}" {description file}`.
7. Create the PR, then hang its prerequisite on it. Run `jsc-gitea/tools/gitea.sh pr-create {owner}/{repo} {target branch} {base branch} "{branch name}" {description file}`. Ask the user to confirm before this call runs.
- Title = branch name.
- Write the description into a temp file first, using `templates/pr-description.md` (a Traditional Chinese template; the generated description stays in Traditional Chinese per the STE100 output rule).
- Exit 0 → the command prints a PR URL; keep it.
@@ -63,8 +63,8 @@ The ladder rules live in one place only: section 「PR 分支階梯」 of `jsc-m
1. Title against the target branch name.
2. Description against a freshly drafted description from `templates/pr-description.md`.
3. Prerequisite PR dependency against the one the description names.
- Title or description differs → write the new description to a temp file and run `jsc-gitea/tools/gitea.sh pr-edit {owner}/{repo} {pr number} "{title}" {description file}`, which carries both items in one call. Exit 0 → updated. Exit 2 (description file not found) → write the file and rerun. Exit 4 or any other non-zero → report the script's message and stop, and say plainly that the PR still holds its old title and description.
- The dependency differs → run `pr-depend` with the exit code branching of step 7.
- Title or description differs → write the new description to a temp file and run `jsc-gitea/tools/gitea.sh pr-edit {owner}/{repo} {pr number} "{title}" {description file}`, which carries both items in one call. Ask the user to confirm before this call runs. Exit 0 → updated. Exit 2 (description file not found) → write the file and rerun. Exit 4 or any other non-zero → report the script's message and stop, and say plainly that the PR still holds its old title and description.
- The dependency differs → run `pr-depend` with the exit code branching of step 7. Ask the user to confirm before this call runs.
- All three match → change nothing. Every needless edit notifies every reviewer, so silence is the correct outcome here.
- Done when each of the three items is reported as either matched or updated, and the number of API calls made equals the number of items that differed.
9. Reply to the handled comments, then report the run.