chore: gitignore .shipyard/ and remove tracked Shipyard state#146
Merged
Conversation
Shipyard runtime artifacts (STATE.json, HISTORY.md, plans, phase directories, lessons, roadmap) are per-machine process state, not project deliverables. Tracking them in git bloats PR diffs to the point where CodeRabbit's free-tier review threshold gets tripped silently — PR #143 (phase-2 inbox foundation) hit exactly this and got no AI review. The clean polling-fix split off PR #143 (see PR #145) demonstrated CodeRabbit reviews fine when .shipyard noise is absent. Going forward: • Plans, lessons, and roadmaps that need to be shared live in CLAUDE.md (Lessons Learned) and docs/. • Shipyard's runtime state stays local-only; share across machines via Dropbox/copy if multi-machine work is needed. • Existing knowledge in .shipyard/LESSONS.md is already mirrored in CLAUDE.md's Lessons Learned section (the canonical source). This commit: • Adds .shipyard/ to .gitignore. • Removes the 130 currently-tracked files under .shipyard/ via git rm. • The .shipyard/ directory remains on the local machine — only the git-tracked copies are removed. Future shipyard sessions can use the directory normally; it just won't show up in PRs. Note for the open PR #143: that branch carries a one-line .coderabbit.yaml (commit cbb8aa3) that excludes .shipyard/** from review scope. With this PR landed, that file is no longer needed and can be dropped during the rebase of PR #143 onto the new master. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (131)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #146 +/- ##
==========================================
- Coverage 89.85% 89.59% -0.26%
==========================================
Files 1000 1000
Lines 29651 29651
Branches 2401 2401
==========================================
- Hits 26643 26566 -77
- Misses 2166 2226 +60
- Partials 842 859 +17 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
3 tasks
blehnen
added a commit
that referenced
this pull request
May 20, 2026
PR #146 added .shipyard/ to .gitignore and removed all tracked files, but one stray phase-7 SUMMARY slipped through. Drop it from tracking; the gitignore rule keeps it out of future commits. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
blehnen
added a commit
that referenced
this pull request
May 20, 2026
PR #146 added .shipyard/ to .gitignore and removed all tracked files, but one stray phase-7 SUMMARY slipped through. Drop it from tracking; the gitignore rule keeps it out of future commits. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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.
Why
Shipyard runtime artifacts (plans, state, lessons, roadmap, phase directories) are process state — not project deliverables. Tracking them in git inflates PR diffs to the point where CodeRabbit's free-tier review threshold gets tripped silently. PR #143 hit exactly this and got no AI review. The clean polling-fix split (PR #145) reviews fine without the
.shipyard/noise.What this PR does
.shipyard/to.gitignore..shipyard/viagit rm..shipyard/directory is preserved on each contributor's machine — only the git-tracked copies are removed. Future Shipyard sessions still work; their artifacts just don't show up in PRs.Not lost
CLAUDE.md's "Lessons Learned" section already mirrors the institutional knowledge from.shipyard/LESSONS.md— that remains the canonical source.docs/on a case-by-case basis as needed.Test plan
dotnet build "Source/DotNetWorkQueue.sln" -c Debugpasses locally (nothing underSource/touched)Follow-up for PR #143
PR #143 (phase-2-inbox-foundation) carries:
.coderabbit.yaml(commitcbb8aa30) that excludes.shipyard/**from review — no longer needed after this lands..shipyard/files that will conflict with the gitignore on rebase.When this PR merges, rebase PR #143 onto the new master and drop both the
.coderabbit.yamlcommit and the.shipyard/additions.🤖 Generated with Claude Code