prek-based pre-commit checks and flake checks #8
No reviewers
Labels
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
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
polyphony/workflows!8
Loading…
Reference in a new issue
No description provided.
Delete branch "flori/prek"
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?
My vision for this repository is for it to turn into our single source of truth for all check declarations, linting rules, formatting configurations and these things. Downstream flakes import this one and, like they do currently, enable the modules they need for their project, such as our
rustmodule.This is a first step towards that. We replace
pre-commitwithprek, which is basically the same tool but heaps faster, more modern and RIIR. In this flake, pre-commit hooks can be defined and added using standardized syntax. In downstream consumers, theprek.tomlwill then dynamically be generated from the enabled/added hooks.I barely have an idea about what I am doing in nix, but the approach is, I think, not dumb.
4eb2dfafeato84ac1a1029