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
Fix: the built-in checks that ask what a Bash or PowerShell command runs (push-check-reminder, private-word-guard, post-push-reminder, public-repo-writing-reminder, wago-verb-reminder, git-add-own-check and turn-state) now all read it the same way, as the shell would.
Quoted text, comments and heredoc bodies are data. A PR body or a commit message that mentions git push (gh pr create --body "$(cat <<'EOF' …)", git commit -F - <<'EOF') is no longer taken for a push.
What is handed to a shell runs and is read: bash -c "…", bash <<'EOF', cat <<'EOF' | bash, and a heredoc written to a script that the command then runs. Substitutions run too.
A cd inside a subshell, a substitution or a function's body counts only there: (cd x) && git push pushes from the working folder.
Whether a push or a gh pr/gh release command runs at all is also still matched against the whole command outside quotes, as before. Only text shown to be data (see "How commands are read" in the README) is left out of that match, so a shell handed text in a way the new reading does not follow still counts.
git-add-own-check now joins lines continued with \. The files listed after a continued line were not checked before.