Skip to content

fix(branch): persist explicit finish bases - #750

Merged
NagyVikt merged 1 commit into
mainfrom
agent/codex/repair-restored-branch-guardex-base-meta-2026-08-31-15-53
Aug 31, 2026
Merged

fix(branch): persist explicit finish bases#750
NagyVikt merged 1 commit into
mainfrom
agent/codex/repair-restored-branch-guardex-base-meta-2026-08-31-15-53

Conversation

@NagyVikt

Copy link
Copy Markdown
Collaborator

Summary

  • fix(branch): persist explicit finish bases

Test plan

  • verified locally

Repair restored lane metadata before finish gates and when reusing a branch with --base.

Constraint: never persist the repo-wide fallback as branch-specific metadata.

Tested: node --test test/git-base-branch.test.js; targeted branch reuse test; npm run lint
@NagyVikt
NagyVikt marked this pull request as ready for review August 31, 2026 14:00

@NagyVikt NagyVikt left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

🛡️ GitGuardex code-assist

1 finding(s) — 🟡 1 medium

Merge gate: pass — no blocking findings (blocks on high/critical).

Severity Location Finding
🟡 medium src/git/index.js:1102-1104 The explicit base is persisted before it is validated. A typo or nonexistent branch can overwrite previously valid branch metadata, causing

Provider codex · commit 5647b49

Comment thread src/git/index.js
@NagyVikt
NagyVikt merged commit 1764b82 into main Aug 31, 2026
4 checks passed
@NagyVikt
NagyVikt deleted the agent/codex/repair-restored-branch-guardex-base-meta-2026-08-31-15-53 branch August 31, 2026 14:05
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