Skip to content

Isolate seed workflow git from operator hooks - #467

Merged
TheGreatAxios merged 4 commits into
mainfrom
cl-7184-seed-workflow-git-commit-is-blocked-by-the-operators-git
Aug 30, 2026
Merged

TheGreatAxios merged 4 commits into
mainfrom
cl-7184-seed-workflow-git-commit-is-blocked-by-the-operators-git

Conversation

@TheGreatAxios

Copy link
Copy Markdown
Contributor

CL-7184 https://linear.app/abklabs/issue/CL-7184/seed-workflow-git-commit-is-blocked-by-the-operators-git-hooks

Connecting a provider persisted the credential but the background seed git commit (author seed@workbench.localhost) inherited the operator's core.hooksPath. A human-email allowlist hook blocked the commit, so Myra never deployed and / stayed on Preparing your agent.

This isolates seed git: empty core.hooksPath on every pusher git invocation, and git commit --no-verify. Regression test plants a rejecting commit-msg hook via GIT_CONFIG_GLOBAL.

@TheGreatAxios TheGreatAxios left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critique · approve

Seed pusher isolates operator git hooks: every runGit is git -c core.hooksPath=, commit is --no-verify. Regression plants a rejecting commit-msg via GIT_CONFIG_GLOBAL and still pushes. CL-6357 force-push of seed-owned main is intact.

GitHub will not accept approve on the author's own PR; this comment is the review.

@TheGreatAxios
TheGreatAxios merged commit 8c72c92 into main Aug 30, 2026
5 checks passed
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