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
{{ message }}
Repository navigation
Commit b6bccdd
Browse filesBrowse the repository at this point in the historyBrowse files
fix: clarify --json flag requirement per Copilot review
- Rephrased step 2 to mention both --short-name and --json flags
- Added explicit note to always include the JSON flag for reliable output parsing
Co-Authored-By: Claude Opus 4.6 <[email protected]>
2.**Create the feature branch** by running the script with only `--short-name` (do NOT pass `--number`— the script auto-detects the next globally available number across all branches and spec directories):
42
+
2.**Create the feature branch** by running the script with `--short-name` (and `--json`), and do NOT pass `--number`(the script auto-detects the next globally available number across all branches and spec directories):
43
43
44
44
- Bash example: `{SCRIPT} --json --short-name "user-auth" "Add user authentication"`
45
45
- PowerShell example: `{SCRIPT} -Json -ShortName "user-auth" "Add user authentication"`
46
46
47
47
**IMPORTANT**:
48
48
- Do NOT pass `--number` — the script determines the correct next number automatically
49
+
- Always include the JSON flag (`--json` for Bash, `-Json` for PowerShell) so the output can be parsed reliably
49
50
- You must only ever run this script once per feature
50
51
- The JSON is provided in the terminal as output - always refer to it to get the actual content you're looking for
51
52
- The JSON output will contain BRANCH_NAME and SPEC_FILE paths
0 commit comments