A new project's proposal plans a .gitignore that Braid adds right after it #286

Closed
opened 2026-10-28 19:06:41 -04:00 by cmoriarty · 1 comment
Owner

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.proposal adds one for the proposal's stack, 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 .gitignore only in passing, in the sidecar's stack note. The file's header still says "Added by openspec-flow", Braid's old name.

Fix

  • The propose brief says plainly: Braid adds a .gitignore for the named stack right after this step, so plan none and don't call it missing.
  • The header says "Added by Braid".

Done when

A new project's proposal plans no .gitignore, and its review raises none about it.

From #279, runs 135 and 136.

**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.proposal` adds one for the proposal's `stack`, 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 `.gitignore` only in passing, in the sidecar's `stack` note. The file's header still says "Added by openspec-flow", Braid's old name. **Fix** - The propose brief says plainly: Braid adds a `.gitignore` for the named stack right after this step, so plan none and don't call it missing. - The header says "Added by Braid". **Done when** A new project's proposal plans no `.gitignore`, and its review raises none about it. _From #279, runs 135 and 136._
Author
Owner

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".

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".
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
cmoriarty/braid#286
No description provided.