Skip to content

fix: .gitignore and CHANGELOG were appended with literal backslash-n - #130

Merged
musharna merged 2 commits into
mainfrom
fix/gitignore-changelog-newlines
Sep 2, 2026
Merged

fix: .gitignore and CHANGELOG were appended with literal backslash-n#130
musharna merged 2 commits into
mainfrom
fix/gitignore-changelog-newlines

Conversation

@musharna

@musharna musharna commented Sep 2, 2026

Copy link
Copy Markdown
Owner

Follow-up to #129. config/projects.local.yaml was not actually ignored (the appended .gitignore line contained literal \n sequences), and CHANGELOG had a second broken [Unreleased] header. Verified: git check-ignore -v config/projects.local.yaml.gitignore:32; one Unreleased header; guard test green.

The privacy commit (#129) wrote both files through a script whose "\\n" was
the two characters backslash-n, not a newline. .gitignore therefore had one
line that matched nothing, so config/projects.local.yaml -- the file that
holds the real roots -- was NOT ignored (git check-ignore printed nothing).
CHANGELOG gained a second, broken [Unreleased] header. Found by the ~/jobd
session's cat -A. Both rewritten with real newlines; check-ignore now
resolves to .gitignore:32.
tests/test_changelog_fragments.py requires [Unreleased] to stay empty; the
broken header from #129 had hidden this entry from that test.
@musharna
musharna merged commit c03f849 into main Sep 2, 2026
7 checks passed
@musharna
musharna deleted the fix/gitignore-changelog-newlines branch September 2, 2026 17:31
@musharna musharna mentioned this pull request Sep 2, 2026
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.

1 participant