Repository navigation
Conversation
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
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.
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-mergereopens both keys once intro's pin moves, since the copy a ruling takes must be its sealed version, and the bibliography check goes red.ModiglianiBrumberg19541b5b4d953cab40931ca767d52640eaedsargent1989leastb5017575cd6e85801bcb74219e915562The 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'sbecausenotes 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:tools/sync --update --pin-only intromoves intro's pin to that merge, andtools/bib-merge --reconstruct --writeregenerateslectures/_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);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