fix(git): scope git-workflow's trigger to ambiguity rather than to its domains
git-workflow's description enumerated the six domains it exists to route away from, so it competed for selection with the very skills it should be handing off to. It now triggers on the case it actually serves: an interactive request whose domain is not yet clear. Also clears frontmatter drift across the plugin and removes duplicated guidance in pc-run that had diverged from its reference.
This commit is contained in:
@@ -23,6 +23,10 @@ A pull that diverges with no strategy configured fails, and that failure is the
|
||||
|
||||
## Config precedence
|
||||
|
||||
The installed default varies by Git version — older versions merge on divergence, newer ones
|
||||
default to `--ff-only` — so an unset `pull.ff` means the same pull behaves differently on different
|
||||
machines. Set it explicitly.
|
||||
|
||||
Highest wins:
|
||||
|
||||
1. Command-line flag (`--ff-only` / `--rebase` / `--no-rebase`)
|
||||
|
||||
Reference in New Issue
Block a user