Repository navigation
fix: stop tracking personal .cursor/skills symlinks - #21
Merged
Merged
Conversation
.cursor/skills/coding-standards and .cursor/skills/dev-tooling were committed as symlinks pointing outside the repo to a machine-local personal skills directory (../../../../personal/personal-skills/...). Every other entry under .cursor/skills is a real, portable directory — these two only ever resolved on the original committer's machine. In CI, actions-gh-pages's publish step (fallow-badge job) copies the whole working directory and fails with ENOENT trying to stat the dangling symlink target. Untracking them (and ignoring the path so they don't get re-added) fixes that without touching anyone's local Cursor setup — the symlinks stay on disk, just no longer version-controlled. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
💤 Files with no reviewable changes (2)
📝 WalkthroughWalkthroughThe PR removes two local Cursor skill reference files and adds ChangesCursor skill cleanup
Estimated code review effort: 1 (Trivial) | ~2 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
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
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.


Summary
.cursor/skills/coding-standardsand.cursor/skills/dev-toolingwere committed as symlinks pointing outside the repo (../../../../personal/personal-skills/...) — a machine-local personal skills directory that only resolves on the original committer's machine. Every other entry under.cursor/skills/is a real, portable directory with its ownSKILL.md.This surfaced as a CI failure in the
fallow-badgejob's "Publish badge" step (see #20):actions-gh-pagescopies the whole working directory to publish the badge, and fails withENOENTtrying tostatthe dangling symlink target on a fresh CI checkout.Fix
git rm --cachedthe two symlinks — they stay on disk locally (your own Cursor setup is unaffected), they're just no longer version-controlled..gitignoreso they don't get accidentally re-added.Test plan
git status/git ls-filesno longer track themactions-gh-pagesto trip over🤖 Generated with Claude Code
Summary by CodeRabbit