Conversation
|
Testing downstream via https://github.com/LM-SAL/aiapy/actions/workflows/update-spec0.yaml Finally got it to open: LM-SAL/aiapy#377 |
|
TODO: Replace the download location to use this repo in the future. |
bsipocz
left a comment
bsipocz
left a comment
There was a problem hiding this comment.
This is water under the bridge, but I think these should be fixed up in follow-up PR(s) and then tagging new releases.
| fi | ||
|
|
||
| - name: Fetch Schedule from release | ||
| uses: robinraju/release-downloader@v1.3 |
There was a problem hiding this comment.
Definitely for the third party actions please use the hashes, but maybe to be consistent do it for everything.
| - name: Fetch Schedule from release | ||
| uses: robinraju/release-downloader@v1.3 | ||
| with: | ||
| repository: "savente93/SPEC0-schedule" |
There was a problem hiding this comment.
we should not rely on a third party location for any SPEC0 related content
There was a problem hiding this comment.
I agree but I need to get the release working on this repo first. Or even if we want to do it in this repo or a separate repo.
2 participants
Updated spec0 file from the specs repo
Added the action to do a release of the schedule in a machine readable format from https://github.com/savente93/spec0-schedule
Added some tests with only setuptools pyproject toml files.