aboutsummaryrefslogtreecommitdiff
path: root/scripts/remove.sh
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-06-03 13:30:35 -0500
committerCraig Jennings <c@cjennings.net>2026-06-03 13:30:35 -0500
commit36e57f15e2cc191172016c50d45b5bf5d71933e5 (patch)
tree609d8df5c28713ee7fadf2e3ba2bfb8feb14d800 /scripts/remove.sh
parent586c8f69b2f1e0498be7f8abecfd348aae12e5dd (diff)
downloadrulesets-36e57f15e2cc191172016c50d45b5bf5d71933e5.tar.gz
rulesets-36e57f15e2cc191172016c50d45b5bf5d71933e5.zip
fix(language-bundle): don't re-drop the coverage fragment once adopted
The startup bundle sync re-dropped from-rulesets-coverage-makefile.txt into a project's inbox on every run, even after the project had adopted the targets. inbox_drop only treated the fragment as adopted if coverage-makefile.txt still sat at the project root or waited in the inbox. But install-lang tells users the opposite: copy the targets into your Makefile, then delete the fragment. So a project that followed the documented path got the drop re-suggested forever (deleted three sessions running in one case). I guarded the drop so a project Makefile that already defines the distinctive coverage-summary target counts as adopted. The check lives at the call site, keeping inbox_drop generic. Added two bats cases: targets-in-Makefile suppresses the drop, an unrelated Makefile still gets it.
Diffstat (limited to 'scripts/remove.sh')
0 files changed, 0 insertions, 0 deletions