polyphony/workflows
polyphony/workflows
Watch
5
5
Fork
You've already forked workflows
 1
Code Issues 2 Pull requests Releases 4 Activity Actions

fix: reuse scans its own module instead of what it is supposed to scan,,, #17

Merged
ava merged 1 commit from flori/fix-reuse into main 2026-07-26 17:40:58 +02:00
Conversation 0 Commits 1 Files changed 3 +60 -3
ava commented 2026-07-26 17:37:48 +02:00
Owner

I accidentally made it so that the reuse scan in the actual check part itself scanned its own module folder, rather than the src of the project it is imported to. This fixes it. Also adds an override for the src path on reuse, as documented.

I accidentally made it so that the reuse scan in the actual check part itself scanned its own module folder, rather than the `src` of the project it is imported to. This fixes it. Also adds an override for the `src` path on `reuse`, as documented.
fix: reuse scans its own module instead of what it is supposed to scan,,,
All checks were successful
Nix: Check flake / nix-flake-check (pull_request) Successful in 2m45s
Details
Nix: Check flake / nix-flake-check (push) Successful in 4m10s
Details
33117568bc
ava scheduled this pull request to auto merge when all checks succeed 2026-07-26 17:40:07 +02:00
ava merged commit 33117568bc into main 2026-07-26 17:40:58 +02:00
ava deleted branch flori/fix-reuse 2026-07-26 17:40:59 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
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
Under Discussion
 This issue needs further discussion before it can be made actionable.

  
👁️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

  
📋️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.

No labels
⚠️Priority
A (Highest)
⚠️Priority
C (High)
⚠️Priority
D (Medium-High)
⚠️Priority
E (Medium)
⚠️Priority
G (Low)
⚠️Priority
H (Lowest)
🏷️Kind
Bug
🏷️Kind
Chore
🏷️Kind
Documentation
🏷️Kind
Epic
🏷️Kind
Feature
🏷️Kind
Improvement
🏷️Kind
Task
🏷️Kind
Testing and CI
👁️Reviewed
Duplicate
👁️Reviewed
Invalid
👁️Reviewed
Under Discussion
👁️Reviewed
Valid
👁️Reviewed
Won't Fix
📋️Kind/Security
📋️Status
Abandoned
📋️Status
Blocked
📋️Status
In Progress
📋️Status
Need More Info
🔧Difficulty
A (Very hard)
🔧Difficulty
B (Hard)
🔧Difficulty
C (Medium)
🔧Difficulty
D (Easy)
🔧Difficulty
E (Trivial)
Compat
Breaking
Good First Issue
Milestone
Clear milestone
No items
No milestone
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!17
No description provided.