Conversation
Users working in local-only feature branches inside VS Code Source Control should not be blocked by protected-branch hooks when no remote/upstream branch exists yet. The hook now keeps protection for shared/remote branches while permitting local-only VS Code commits, and codex-session protection remains unchanged. Constraint: Codex/OMX sessions must stay blocked on protected branches Rejected: Keep TERM_PROGRAM=vscode as VS Code context signal | over-matches terminal sessions and weakens branch guardrails Rejected: Allow all protected-branch VS Code commits | would permit unsafe writes on shared protected branches Confidence: high Scope-risk: narrow Reversibility: clean Directive: Keep local-only exception tied to both missing upstream and missing remote counterpart Tested: node --test test/install.test.js; npm test
…ranch-commit-allowance
NagyVikt
deleted the
agent/codex/pia-edix-hu-dup-2-vscode-local-branch-commit-allowance
branch
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
1 participant
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.
Summary\n- allow VS Code Source Control commits on protected branches that exist only locally (no upstream and no remote counterpart)\n- keep protected-branch blocking for shared/remote branches and for Codex/OMX sessions\n- stop using TERM_PROGRAM=vscode as a VS Code SCM signal to avoid terminal false positives\n\n## Validation\n- node --test test/install.test.js\n- npm test