Repository navigation
Assign algorithm identifiers locally before merge - #101
Open
domguinard wants to merge 4 commits into
Open
domguinard wants to merge 4 commits into
domguinard wants to merge 4 commits into
Conversation
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.
Contributors currently have to guess numeric identifiers, which can collide between simultaneous submissions. New entries may now omit
identifier; after review, a maintainer runspython3 .github/scripts/registry.py --assign --base-ref origin/main, commits the assigned IDs to the same PR, and merges after validation. The command assigns consecutive IDs above the target list's maximum, replaces new entries' provisional IDs, preserves existing identity fields, and validates the result before writing.validate-jsonaccepts ID-less new entries. The separatepublish-readycheck requires complete, unique IDs. Both checks reject duplicate algorithm names and changes to published identity fields. The public schema remains strict. Maintainers fetch and integrate the current target branch before assigning IDs and process registrations sequentially; if another registration merges first, update the branch and rerun assignment. IDs remain provisional until merged.This uses a local command and read-only CI. There is no allocation bot, privileged workflow, label trigger, reservation ledger, or second registration PR. The README documents the contributor and maintainer steps.
Validation
Setup after merge
Require both
validate-jsonandpublish-ready, with branches required to be up to date before merging. Keep normal human review requirements. No bot credentials, labels, state branch, or write-enabled workflow settings are needed. Repository protection settings are documented, not changed by this PR.