At all steps, SeaGOAT is developed with the intention of guaranteeing Windows support. That being said, as I don't have a Windows device and I don't have expertise regarding Windows development workflows, I have not been able to verify that it works properly on Windows.
The main goal is to support WSL, but supporting Windows natively is also a goal if it's possible!
Help wanted!
Here is a rough checklist of the current status of Windows support:
Also, I have discovered that some of the tests are failing on Windows. So, I created a CI file specifically for Windows that only checks some of the tests that are passing without issue:
|
- name: Run pytest |
|
run: | |
|
poetry run pytest tests/test_repository.py -vvs --timeout=60 |
For comparison, the Linux tests look like this:
|
- name: Run pytest |
|
run: | |
|
poetry run pytest . -vvs --timeout=60 |
At all steps, SeaGOAT is developed with the intention of guaranteeing Windows support. That being said, as I don't have a Windows device and I don't have expertise regarding Windows development workflows, I have not been able to verify that it works properly on Windows.
The main goal is to support WSL, but supporting Windows natively is also a goal if it's possible!
Help wanted!
Here is a rough checklist of the current status of Windows support:
Also, I have discovered that some of the tests are failing on Windows. So, I created a CI file specifically for Windows that only checks some of the tests that are passing without issue:
SeaGOAT/.github/workflows/test-windows.yml
Lines 56 to 58 in 1edae8e
For comparison, the Linux tests look like this:
SeaGOAT/.github/workflows/test.yml
Lines 56 to 58 in 1edae8e