Skip to content

sync/bib.yml: re-seal intro's two take rulings for its converged copies - #88

Draft
mmcky wants to merge 1 commit into
mainfrom
bib/reseal-intro
Draft

mmcky wants to merge 1 commit into
mainfrom
bib/reseal-intro

Conversation

@mmcky

@mmcky mmcky commented Nov 22, 2026 •

Copy link
Copy Markdown
Contributor

What

QuantEcon/lecture-python-intro#875 sets intro's copy of every entry a ruling covers to the pool's result (the owner's "All ruled entries (Recommended)", 2026-11-22). Two rulings take intro's copy, so their seals must name the new copy. Otherwise tools/bib-merge reopens both keys once intro's pin moves, since the copy a ruling takes must be its sealed version, and the bibliography check goes red.

Ruling intro's seal before after
ModiglianiBrumberg1954 1b5b4d953cab4093 1ca767d52640eaed
sargent1989least b5017575cd6e8580 1bcb74219e915562

The digests are tools/bib-merge's own, of intro's copies as QuantEcon/lecture-python-intro#875 writes them; the organiser's reviewer reproduced both. Each ruling's because notes the re-seal. The merged entries do not change. Every other series' copy of these keys either keeps its sealed version or, once its own pull request merges, equals the result, which the tool accepts either way.

Order (draft until it can pass)

This cannot pass until intro's pin names QuantEcon/lecture-python-intro#875's merge, because its CI reconstructs intro's bibliography at the pin in sync/state.yml. So the pin moves in this pull request itself, with no separate sync run:

  1. bibliography: set the 42 ruled entries to the lecture monorepo's lecture-python-intro#875 merges;
  2. on this branch, tools/sync --update --pin-only intro moves intro's pin to that merge, and tools/bib-merge --reconstruct --write regenerates lectures/_static/quant-econ.bib, whose header records the rulings' digest and the inputs (only intro's input and the rulings' digest change; the entries do not);
  3. its CI goes green, and it merges before the nightly sync (03:47 UTC).

Moving the pin here, not by a run of sync.yml, means the bibliography check never goes red and no bot refresh pull request opens against this one. QuantEcon/lecture-python.myst#1140 and QuantEcon/lecture-python-advanced.myst#420 should wait until this has merged: a sync that moved their pins first would reopen their own take rulings here.

The re-seals for intermediate's six and advanced's six take copies that change (QuantEcon/lecture-python.myst#1140, QuantEcon/lecture-python-advanced.myst#420) follow the same way when those merge. jax takes no ruling, and dp is not a source.

🤖 Generated with Claude Code

https://claude.ai/code/session_01WT8bMacV9Lmy1VLUc6XJoL

QuantEcon/lecture-python-intro#875 sets intro's copies of every ruled
entry to the pool's result. ModiglianiBrumberg1954 and sargent1989least
take intro's copy, so their seals must name the new copy, or
tools/bib-merge reopens both keys once intro's pin moves (the copy a
ruling takes must be its sealed version). The digests are tools/bib-merge's
own, of intro's copies as #875 writes them. The results do not change.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WT8bMacV9Lmy1VLUc6XJoL
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