Repository navigation
Promote gives the Hub's main the version's files - #11
Merged
Merged
Conversation
…page and viewer show it, and a candidate holds only its own output Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
The Hub's dataset page and viewer show
main, whichpromotenever moved, so every published dataset looked empty there (jaffe-paired,oplm-antibody-sequences, andhelloon the dev org:mainholds only.gitattributes; each version's files are under its tag).scripts/promote, after tagging, makes one commit onmainthat deletes what the version lacks and copies in the version's files on the Hub (no upload). Nothing whenmainalready holds them, so a second run stays harmless and running it again backfills a version promoted before this.parent_commitis themainit read, so a concurrent change fails rather than being overwritten. The tag stays the version;mainis a copy for browsing, not the tagged commit, since the Hub moves a branch only by a commit. The last line is unchanged, so flyloft needs no change.scripts/pushpassesdelete_patterns="*": a candidate branches frommain, which now holds the last version, so what the new output lacks is deleted and the candidate still holds exactly the record's files (.gitattributesthe library never deletes; the card is rewritten next).list_repo_treeandcreate_commit. Three new tests: a push over a published version holds only the new output; promote givesmainthe version's files; promote of a version published beforemainfollowed moves it. The run-again test also checks no commit is made.python3 -I -m unittest discover tests: 46 OK. Not yet run against the real Hub: the backfill ofhelloonbrineylab-devis the first live run, beforejaffe-pairedandoplm-antibody-sequences.🤖 Generated with Claude Code