A new project's proposal plans a .gitignore that Braid adds right after it #286
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What happens
On a new project, the proposal says "there is currently no
.gitignore" and plans a task to add one. Right after propose,script.gitignore.proposaladds one for the proposal'sstack, so the claim is stale before review and the task would overwrite Braid's file. In run 136 the reviewer caught it, which cost a finding and a revision; run 135's apply found the task "already added by the orchestrator". The propose brief mentions the.gitignoreonly in passing, in the sidecar'sstacknote. The file's header still says "Added by openspec-flow", Braid's old name.Fix
.gitignorefor the named stack right after this step, so plan none and don't call it missing.Done when
A new project's proposal plans no
.gitignore, and its review raises none about it.From #279, runs 135 and 136.
Shipped in PR #297 (
1d98b25). The propose brief now says: "When the repository has no.gitignore, Braid writes one for this stack right after this step. Do not plan one, and do not call it missing." The file's header says it was added by Braid.Verified on run 137 (a new project on llama.cpp): its proposal and tasks don't mention a
.gitignore, and the one Braid wrote after the step begins "added by Braid".