flake: use flake-parts (#1208)

Link: https://github.com/danth/stylix/pull/1208

Reviewed-by: Matt Sturgeon <matt@sturgeon.me.uk>
Reviewed-by: NAHO <90870942+trueNAHO@users.noreply.github.com>
This commit is contained in:
awwpotato 2025-05-16 11:52:15 -07:00 committed by GitHub
parent 49b1eb9371
commit 8b015b5fa0
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
9 changed files with 273 additions and 241 deletions

View file

@ -11,13 +11,14 @@ To keep things consistent, commit messages should follow a format
Where the scope is one of:
| Scope | Purpose |
|----------------|------------------------------------------------------------------------|
| `ci` | Changes to GitHub Actions workflows. |
| `doc` | Changes to the website, `README.md`, and so on. |
| `stylix` | Changes in the `stylix` directory, `flake.nix`, and other global code. |
| Name of target | Changes to code for a particular target. |
| `treewide` | Changes across many targets. |
| Scope | Purpose |
|----------------|------------------------------------------------------------------|
| `ci` | Changes to GitHub Actions workflows. |
| `doc` | Changes to the website, `README.md`, and so on. |
| `flake` | Changes in the `flake` directory, `flake.nix`, and `flake.lock`. |
| `stylix` | Changes in the `stylix` directory and other global code. |
| Name of target | Changes to code for a particular target. |
| `treewide` | Changes across many targets. |
The scope is meant to indicate which area of the code was changed. Specifying
the type of change, such as `feat` or `fix`, is not necessary. Dependency