feat: add REUSE workflow organization template - #9
Merged
Merged
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
1 participant
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.
Summary
Add
reuse.ymlas the first low-risk Nextcloud-derived workflow template managed end to end by this repository.Upstream tracking
The source is tracked from
nextcloud/.github/workflow-templates/reuse.ymlusing:upstream/vendor/nextcloud/.LibreCode adaptation
Nextcloud runs this workflow on
ubuntu-latest-low, which is specific to their runner environment.LibreCode applies a minimal downstream patch:
The generated result is committed as:
workflow-templates/reuse.ymlworkflow-templates/reuse.properties.jsonTemplate metadata is LibreCode-owned and uses a GitHub Octicon, so we do not inherit upstream branding assets.
Why this workflow
REUSE is intentionally the first consumer-facing template because it has low operational risk and lets us validate the entire import → patch → render → catalog → consumer update path before migrating release or credential-sensitive workflows.
Follow-up: #7 will publish the generated template to
LibreCodeCoop/.githuband validate the first consumer repository.