Order the targets in available_software.py #447
Conversation
These names get generated by Javascript maybe it is easiest to add a test in the CI to check if the number of colums correspond with the data in the json files.
|
Tested new workflow here, laraPPr#1. I hope the workflow will be triggered for the update available scripts pr once this pr gets merged. I'm not sure why it is not triggering the workflow in this pr. |
|
And the tests of the available_software.py also do not seem to be running but I ran them locally. |
|
The test for the changed available_software.py script are ran see https://github.com/EESSI/docs/actions/runs/14799376763 |
There was a problem hiding this comment.
This workflow didn't run (as expected, given run the conditions), but it did run in @laraPPr's branch and works well: https://github.com/laraPPr/EESSI_docs/actions/runs/14799375963, so it's safe to assume it will run well when the conditions are met in the target branch.
Co-authored-by: Pedro Santos Neves <10762799+Neves-P@users.noreply.github.com>
|
The linter is failing on yo docstring |
Co-authored-by: Lara Ramona Peeters <49882639+laraPPr@users.noreply.github.com>
Sorry about that! Pushed your suggestions now, hopefully it passes now 👍 |
3 participants
Also needed to fix the tests to take the ordering into account