feature-factory 0.10.5 → 0.10.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/WORKFLOW.md +6 -0
- package/package.json +1 -1
package/WORKFLOW.md
CHANGED
|
@@ -909,6 +909,12 @@ with `git check-ref-format --branch "$FEATURE_BRANCH"`. Bind
|
|
|
909
909
|
`git -C "$O" show-ref --verify --quiet "$FEATURE_REF"` to exit exactly 1 for ref absence. Exit 0 means
|
|
910
910
|
present and every other result is a lookup error; either refuses before init.
|
|
911
911
|
|
|
912
|
+
Bind `KEY` from how `R` was bound, never from anything else: when the configured resolver returned a
|
|
913
|
+
payload, `KEY` is exactly `R`, its `run_id`; when `R` is a ticket key from the request or branch, `KEY`
|
|
914
|
+
is that key; when `R` was derived from free text, `KEY` is absent and `--issue` is omitted. Never add a
|
|
915
|
+
`#` or other decoration. `issue_key` is immutable after init, and publication reads it for the title
|
|
916
|
+
prefix and closing reference, so a run whose resolver found issue `25` must record `25`.
|
|
917
|
+
|
|
912
918
|
An explicit `PR_BASE` wins. Otherwise require the symbolic branch in the configured operator worktree;
|
|
913
919
|
detached, missing, escaping, or unprovable worktree state is refused by init. Request one fresh sandbox
|
|
914
920
|
by running exactly the command below, command first, including each bracketed flag only when its value
|