Conversation
Collaborator
|
we merged #7 so I will close this for now |
Collaborator
Author
|
Reopening — PR #7 (which led to closing this) only addresses the filename of an upstream LICENSE file (LICENSE.txt, COPYING, etc.). It does NOT cover repos where there is no |
jorgeMFS
force-pushed
the
add-license-text-field
branch
from
May 21, 2026 10:02
30a0f41 to
9a5b570
Compare
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.
Adds an optional license.text field to the recipe schema. When a recipe sets it, the hub stores that text verbatim as the LICENSE artifact in the registry instead of fetching one from the upstream repo. This unblocks recipes for tools whose upstreams carry the license in a source-file header rather than a standalone LICENSE file (lh3/wgsim is the immediate motivating case, but the same shape applies to plenty of small bioinformatics utilities).
Merge order
sbom-implementationis the priority branch and rewrites parts of the builders. This PR conflicts with it onhub/builders/builder.pyandhub/validate/validate.py. Rebase after it lands.Also worth a look: this targets
dev, which is currently identical tomaster. Ifdevis defunct this should be retargeted.