Repository navigation
fix(push): never push an agent change to .github - #28
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The protected-path hold ran only before the merge, after ghafk had already pushed the agent's branch. A pushed branch that adds or changes a workflow under
.github/runs in GitHub Actions with the repository's secrets, so a prompt-injected worker or repair could run code with those secrets before any hold or review.--no-renames -z, as the merge hold does). If any is under.github/, it does not push; it parks the issue with the file list and the patch (clipped to 20 000 characters) so the owner can apply it by hand..ghafk/changes are still pushed and held before the merge, since pushing them runs nothing.