Handle collection with multiple releases#11
Merged
Merged
Conversation
JeanMainguy
force-pushed
the
multirelease
branch
from
c785e73 to
c51d71a
Compare
JeanMainguy
approved these changes
Jun 17, 2026
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
2 participants
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.
Handle collection with multiple releases.
Add two filter option in search-pangenomes commandes
--latest-onlyto search only in latest release of each collection.--release-versionto filter pangenomes to a specific collection release version (e.g. '1.0.0').logs have been refined accordingly to this new filters and README.md has been updated.