Repository navigation
Conversation
QuantEcon/lecture-python.myst#1140 sets intermediate's copy of every entry a ruling covers to the pool's result. Six rulings take intermediate's copy and change it, so their seals now name the new copy (digests from tools/bib-merge's own code, of intermediate's copies at 148a901). The merged entries 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.myst#1140 sets intermediate's copy of every entry a ruling covers to the pool's result (the owner's "All ruled entries (Recommended)", 2026-11-22). Six rulings take intermediate's copy and change it, so their seals must name the new copy. Otherwise
tools/bib-mergereopens all six once intermediate's pin moves, since the copy a ruling takes must be its sealed version, and the bibliography check goes red.AKR1990a229f98efbe3e2570517d1216224e38ahansen2020twisted3521470dba8bdbc012c2453dc0203a9fHansenRichard19873bbc65ca3cdefc33dff11e9d6d462585Helpman1985cf417eed8a3dacef26992dc65b708457MarcetMarshall19925bc8e38b782615e61340b06a614cbba3pareto1896cours3af6b01cc3c7cc6c04762a3685a82856The digests are
tools/bib-merge's own, of intermediate's copies at QuantEcon/lecture-python.myst#1140's head,148a901. Each ruling'sbecausenotes the re-seal. The merged entries do not change. Every other ruling that takes intermediate's copy still matches its seal, so no other one reopens.Checked
A simulation with
tools/bib-merge's own code:148a901and every other series at its pin: no refusals;52ea526, advanced at bibliography: set the 38 ruled entries to the lecture monorepo's lecture-python-advanced.myst#420's944bb48and intermediate at148a901: no refusals.--writethen changes only sync/bib.yml: re-seal advanced's six take rulings; brace two titles #89's two braced entries and the header:% inputs:intermediate=06466b7d241875b4.Order (draft until it can pass)
This cannot pass until intermediate's pin names QuantEcon/lecture-python.myst#1140's merge, because its CI reconstructs intermediate's bibliography at the pin in
sync/state.yml. It also waits for #88, which changes the same header. So:tools/sync --update --pin-only intermediatemoves intermediate's pin to #1140's merge (it writes onlysync/state.yml), andtools/bib-merge --reconstruct --writeregenerateslectures/_static/quant-econ.bib, whose header must then readintermediate=06466b7d241875b4;lectures/runs, and it merges before the next nightly sync (03:47 UTC), best straight after #1140. A nightly sync between the two would move intermediate's pin on main by itself, and the bibliography check would go red with these six refusals until this merges.The pin covers every change merged to intermediate's main by then, not only #1140. Moving it changes no lecture in the pool here: drift-check reports any promoted lecture those changes touch as a refresh, and its refresh pull request brings them, reviewed as usual. At step 3 this body lists the upstream changes the new pin covers. The dates in the
becausenotes are those of this draft; they are corrected at step 3 if #1140 merges on a later day (UTC).This and #89 can go in either order after #88; whichever goes second is rebased on the first.
🤖 Generated with Claude Code
https://claude.ai/code/session_01WT8bMacV9Lmy1VLUc6XJoL