Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Write module tests #21

Open
Frontear opened this issue Nov 14, 2024 · 1 comment
Open

Write module tests #21

Frontear opened this issue Nov 14, 2024 · 1 comment
Labels
compat: backwards Represents a backwards compatible change. Existing functionality is wholly unaffected by changes. priority: low Non-essential issues that are neither affecting functionality nor usability. type: feature/addition Marks the request/implementation of a feature addition. Accompany with relevant labels.

Comments

@Frontear
Copy link
Owner

This would be a cool exercise into building decent quality and polished software using nix flake check, and pkgs.testers stuff. A very far off day.

@Frontear Frontear added the priority: low Non-essential issues that are neither affecting functionality nor usability. label Nov 14, 2024
@Frontear
Copy link
Owner Author

Frontear added a commit that referenced this issue Nov 14, 2024
This will build all my configurations and run `nix flake check`. I'm hoping to eventually move the "build" logic into something in the `checks` flake ouput, which would allow `nix flake check` to handle it for me. #21 tracks that progress at the moment.

I had to add a disk-space free action in order to create enough space on the action runner. This could pose a problem for the future..
@Frontear Frontear added type: feature/addition Marks the request/implementation of a feature addition. Accompany with relevant labels. compat: backwards Represents a backwards compatible change. Existing functionality is wholly unaffected by changes. labels Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compat: backwards Represents a backwards compatible change. Existing functionality is wholly unaffected by changes. priority: low Non-essential issues that are neither affecting functionality nor usability. type: feature/addition Marks the request/implementation of a feature addition. Accompany with relevant labels.
Projects
None yet
Development

No branches or pull requests

1 participant