mirror of
https://github.com/harvard-edge/cs249r_book.git
synced 2026-05-06 17:49:07 -05:00
[PR #1373] [MERGED] fix(ci): unblock book-validate by grandfathering 29 bib violations #5155
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/harvard-edge/cs249r_book/pull/1373
Author: @profvjreddi
Created: 4/17/2026
Status: ✅ Merged
Merged: 4/17/2026
Merged by: @profvjreddi
Base:
dev← Head:fix/book-validate-bib📝 Commits (1)
3757e99chore(bib): grandfather 29 missing-publisher @inproceedings entries📊 Changes
1 file changed (+180 additions, -0 deletions)
View changed files
📝
book/tools/bib_lint_baseline.json(+180 -0)📄 Description
Summary
book-validate-dev.ymlhas been failing on everydevpush since 2026-04-13 (run 24346051021) because thebib-lintpre-commit hook reports 29 NEW violations beyond the baseline — all the same rule:These entries are in paper-companion bibs that were added/extended over recent merges:
periodic-table/paper/references.bib— 20 entriesinterviews/paper/references.bib— 9 entriesBoth files already have grandfathered entries for the exact same rule (33 and 5 respectively), so extending the baseline is consistent with the established pattern for paper-companion bibs. The pre-commit config comment explicitly sanctions this:
What changed
book/tools/bib_lint_baseline.json— +180 lines (29 additive entries, allmissing-required-field/publisher). No.bibfiles modified.Verification
Follow-up (not this PR)
If the project decides it wants actual publisher values on these entries rather than grandfathered-silence, that's a separate bib metadata sweep (lookup + add
publisher = {...}per conference). Out of scope here — this PR only restores the green badge.🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.