Skip to content

merge queue: checking main (a9c99b2) and #256 together - #257

Closed
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/c62161cabc
Closed

merge queue: checking main (a9c99b2) and #256 together#257
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/c62161cabc

Conversation

@mergify

@mergify mergify Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

⏳ The pull request #256 is queued for merge and currently being checked. ⏳

Branch main (a9c99b2) and #256 are queued together for merge.

This pull request has been created by Mergify to check the mergeability of #256.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule default for merge:

Required conditions to stay in the queue:

---
checking_base_sha: a9c99b2b12214c90725488ff9320a3ce55e0a5cb
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 256
    scopes: []
scopes: []
...

Liu233w and others added 2 commits July 29, 2026 03:02
…riable

Pinning `git -C` deadened every permission grant in this skill's own frontmatter.
Bash rules match on command prefix, so `git -C <root> status --short` does not
begin with `git status`, and the six `Bash(git …:*)` entries stopped matching the
moment the pin landed — every state-gathering command now prompts. Adds
`Bash(git -C:*)`, plus the commands the body actually prescribes and the earlier
list omitted: show, rebase, checkout, reset, rev-list for the squash and
verification flows, cp for fixup scoping, and ./doit.sh for the per-commit checks.

`python3` and `sed` stay unlisted on purpose. Both appear in the body, but
pre-approving arbitrary code execution for the whole turn is a bad trade in a
commit skill; the prompt is proportionate friction.

Resolving the root from the skill's base dir is right — a literal breaks under
worktrees — but carrying it in `ROOT=` is not: shell state does not persist between
tool calls, and three independent read commands are exactly what gets split into
parallel calls. `$ROOT` is then empty and `git -C ""` falls back to the drifted
cwd, reinstating the bug the pin exists to prevent while looking defended against
it. The resolved path is now substituted into each command directly.
@mergify mergify Bot closed this Jul 28, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/c62161cabc branch July 28, 2026 17:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant