Skip to content

feat(gitignore): do not ignore check outputs the upstream reads from the committed repo - #2553

Merged
dyoshikawa merged 4 commits into
mainfrom
resolve-scrap-issue-2487-committed-check-outputs
Aug 1, 2026
Merged

feat(gitignore): do not ignore check outputs the upstream reads from the committed repo#2553
dyoshikawa merged 4 commits into
mainfrom
resolve-scrap-issue-2487-committed-check-outputs

Conversation

@dyoshikawa

Copy link
Copy Markdown
Owner

Summary

Decides #2487, taking its option 1: Cursor Bugbot and Rovo Dev's code reviewer read .cursor/BUGBOT.md / .rovodev/.review-agent.md from the committed repository — gitignoring them (the blanket generated-outputs rule) disabled the very feature the checks adapters generate. Consistent with the call PR #2545 made for the repo-committed .rovodev/config.yml/mcp.json.

Testing

  • pnpm cicheck green (incl. check:gitignore drift on the regenerated file; all gitignore-derive tests pass).

Closes #2487

🤖 Generated with Claude Code

cm-dyoshikawa and others added 4 commits July 31, 2026 19:08
…the committed repo

Decides #2487 (option 1): Cursor Bugbot and Rovo Dev's code reviewer
only see .cursor/BUGBOT.md and .rovodev/.review-agent.md when they are
checked into the repository, so gitignoring them disabled the very
feature the checks adapters generate.

- New committedOutput meta flag on the checks factory (documented for
  future adapters like Goose .agents/checks/), consulted by
  gitignore-derive: flagged outputs are skipped from derivation.
- Derived .gitignore regenerated: the **/.cursor/BUGBOT.md and
  **/.rovodev/.review-agent.md entries are gone.
- Docs: the Cursor checks note states the commit-to-activate behavior
  for both tools.

Closes #2487

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…rive paths

Review follow-ups on PR #2553: deriveFileEntries gets the same
committedOutput guard as deriveDirEntries (symmetry, in case checks
ever moves derivation shape), and gitignore-entries.test.ts pins that
neither committed check output is ever derived and that the flag stays
meaningful (at least one checks factory sets it).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@dyoshikawa
dyoshikawa merged commit 00a024e into main Aug 1, 2026
9 checks passed
@dyoshikawa

Copy link
Copy Markdown
Owner Author

@dyoshikawa Thank you!

@dyoshikawa
dyoshikawa deleted the resolve-scrap-issue-2487-committed-check-outputs branch August 1, 2026 03:16
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.

Decide whether check outputs read from the committed repo (.cursor/BUGBOT.md, .rovodev/.review-agent.md) should be gitignored by derivation

2 participants