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

Add CI workflow #10

Open
eureka-cpu opened this issue Aug 6, 2024 · 2 comments
Open

Add CI workflow #10

eureka-cpu opened this issue Aug 6, 2024 · 2 comments
Labels
workflow Anything related to GitHub actions

Comments

@eureka-cpu
Copy link
Contributor

The flake checks can be the same as what's in the cloud-reaper workflow file. Other checks should run parts of nix-watch itself and look for specific things, e.g:

nix-watch -c
touch <some file>

should cause the current process to be killed, resulting in an error: interrupted by user if the process takes long enough. If the output of nix-watch is captured to a file, a grep of the file for that error could be one way of checking it's working. Another way to test that the -c, --clear flag works would be to check the status of the PID.

@eureka-cpu eureka-cpu added the workflow Anything related to GitHub actions label Aug 6, 2024
andrewvious added a commit that referenced this issue Aug 12, 2024
Ref #10 

This PR only handles the workflow for basic Nix related checks.
@eureka-cpu
Copy link
Contributor Author

eureka-cpu commented Aug 15, 2024

There's a bash testing framework called bat that could aid in testing functionality. This could be its own issue though so I'll link that here.

@eureka-cpu
Copy link
Contributor Author

#19

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
workflow Anything related to GitHub actions
Projects
None yet
Development

No branches or pull requests

1 participant