polyphony/workflows
10
5
Fork
You've already forked workflows
1

License header checks (REUSE) #4

Closed
opened 2026年04月05日 16:02:08 +02:00 by ava · 1 comment
Owner
Copy link

Being REUSE compliant would be nice. Since we are using MPL-2.0 in most of our repos, it is especially important to include a license header in every file, since MPL-2.0 copyleft is file-based. I believe there is a pre-commit REUSE tool which we can use for this. The other, already existing license header check should be removed, since it has been broken for ages.

Acceptance Criteria

  • REUSE compliance checks in target repository at nix flake check-time.
  • Fail check on missing license header
  • Also apply REUSE checks for this repository itself
Being `REUSE` compliant would be nice. Since we are using MPL-2.0 in most of our repos, it is especially important to include a license header in every file, since MPL-2.0 copyleft is file-based. I believe there is a pre-commit REUSE tool which we can use for this. The other, already existing license header check should be removed, since it has been broken for ages. ## Acceptance Criteria - REUSE compliance checks in target repository at `nix flake check`-time. - Fail check on missing license header - Also apply REUSE checks for this repository itself
Author
Owner
Copy link

Implemented in #10

Implemented in #10
Sign in to join this conversation.
No Branch/Tag specified
main
flori/crane
flori/improvements
No results found.
Labels
Clear labels
⚠️Priority
A (Highest)
 Highest priority issue
⚠️Priority
C (High)
 High priority issue
⚠️Priority
D (Medium-High)
 Medium to high priority issue
⚠️Priority
E (Medium)
 Medium priority issue
⚠️Priority
G (Low)
 Low priority issue
⚠️Priority
H (Lowest)
 Lowest priority issue
🏷️Kind
Bug
 Something is not as expected. For specifications or guidelines, an under-/overspecification is also considered a bug.
🏷️Kind
Chore
 Regular maintainance tasks, version bumps, lint fixes
🏷️Kind
Documentation
 Documentation changes
🏷️Kind
Epic
 This issue is a collection of other, related issues.
🏷️Kind
Feature
 New functionality
🏷️Kind
Improvement
 Improve existing functionality
🏷️Kind
Task
 A specific work item. Can be part of an epic
🏷️Kind
Testing and CI
 Change related to CI or testing
👁️Reviewed
Duplicate
 This issue or pull request already exists
👁️Reviewed
Invalid
 Invalid issue
👁️Reviewed
Valid
 This issue has been reviewed and a resolution is desired
👁️Reviewed
Won't Fix
 This issue won't be fixed
📋️Kind/Security
This is security issue

Archived

📋️Status
Abandoned
 Somebody has started to work on this but abandoned work
📋️Status
Blocked
 Something is blocking this issue or pull request

Archived

📋️Status
In Progress
 This label is intended to be used when an outside collaborator is pursuing the completion of this issue, since they cannot be directly assigned to the task.
📋️Status
Need More Info
 Feedback is required to reproduce issue or to continue work
🔧Difficulty
A (Very hard)
 Measure of time-to-implement and cognitive complexity of the task. "Hard" tasks usually take >15h to complete. Extremely unlikely to be suitable for first-time-contributors.
🔧Difficulty
B (Hard)
 Measure of time-to-implement and cognitive complexity of the task. "Hard" tasks usually take 3h-15h to complete. Very likely not suitable for first-time-contributors.
🔧Difficulty
C (Medium)
 Measure of time-to-implement and cognitive complexity of the task. "Medium" tasks usually take 30min-3h to complete. Likely not suitable for first-time-contributors.
🔧Difficulty
D (Easy)
 Measure of time-to-implement and cognitive complexity of the task. "Easy" tasks usually take 15-30min to complete. Likely suitable for first-time-contributors.
🔧Difficulty
E (Trivial)
 Measure of time-to-implement and cognitive complexity of the task. "Trivial" tasks usually take 1-15min to complete. Very likely suitable for first-time-contributors.
Compat
Breaking
 Breaking change that won't be backward compatible
Good First Issue
This issue is a good task to take on if you are new to the project or the repository and looking to contribute.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
polyphony/workflows#4
Reference in a new issue
polyphony/workflows
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?