Repository navigation
The merger promotes, with their own Hub token - #3
Merged
Merged
Conversation
…omote refuses a record that is not on main; CI holds no Hub token Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… says to run from a full clone; plan A defers to the revised promote 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.
A Hub token belongs to a person, not the org, so CI no longer holds one.
.github/workflows/datasets.yml: thepromotejob and the push trigger are removed.checkon pull requests is unchanged; it reads the public Hub API and needs no token.scripts/promote: after the merge, whoever merged runs it with their ownHF_TOKEN, aspushalready works for the cook. It now refuses a record that isn't onorigin/main(or differs from it), so only a reviewed, merged record gets tagged. This guard has a test:test_promote_refuses_a_record_that_is_not_on_main.promoteworkflow bullet with a paragraph on promoting.promotewith the token it already holds, and reads its last line.hellov1.0.0 was promoted this way, and re-runningpromoteon it through the guard reports "already promoted".flyloft's side: its dataset flow has to call
scripts/promoteafter merging, instead of watching apromotecheck.🤖 Generated with Claude Code