Skip to content

Conversation

@IanHollow
Copy link
Contributor

WIP Improving the vscode theme


@stylix-automation stylix-automation bot added the topic: modules /modules/ subsystem label Nov 18, 2025
@trueNAHO
Copy link
Member

Btw, you can also locally test your Stylix branch without remotely pushing with something like:

inputs.stylix.url = "git+file:///home/user/path/to/stylix";

or

inputs.stylix.url = "path:///home/user/path/to/stylix";

The documentation also mentions this, although the path: protocol is not mentioned because it is a relatively new nix feature:

## Development setup
Currently the easiest way to test Stylix is to use the new code in your actual
configuration.
You might find it useful to override Stylix' input flake reference on your
flake, from `github:nix-community/stylix` to
`git+file:/home/user/path/to/stylix`, so that you don't need to push changes to
GitHub during testing.
To do that, instead of editing your `flake.nix`, you can leverage `nix`'
`--override-input` parameter (which can also be supplied through their
frontends: `nixos-rebuild`, `nix-on-droid` and even `nh`). It allows you to
deploy your changes in one fell swoop, without having to update the lock file of
your flake every time you make an edit.
Just append `--override-input stylix git+file:/home/user/path/to/stylix` to your
standard `nix` (or `nix` frontend) incantation.
Nix only reads files which are tracked by Git, so you also need to `git add
«file»` after creating a new file.

@stylix-automation stylix-automation bot added the status: merge conflict Merge conflict label Dec 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

status: merge conflict Merge conflict topic: modules /modules/ subsystem

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants