You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
gh run download -R 'https://github.com/Fabricators-of-Create/Create' $(gh run list -R 'https://github.com/Fabricators-of-Create/Create' -b mc1.18/fabric/dev -w build -L 1 --json databaseId --jq '.[0].databaseId')
using this command, you can download Create's action articifact.
The requirement for other similar are
github link https://github.com/Fabricators-of-Create/Create
branch name mc1.18/fabric/dev
workflow name build
And this should work!
(But create has two files in Artificats, one source, and another one normal. This would also require Implement filtering for GitHub releases. #29
to be implemented. Or else it would probably use the wrong file)
Although the use of gh is not that good here. It should technically be possible to do this via pure curl, but I'm not that good at it.
And for upgrading action files, I got an idea.
Save the current commit hash(not the actual file hash, but the github commit hash)
And if the current commit hash doesn't equal to upstream's commit hash, update.
I put this feature in discussions because it's such a strange feature and strange solution that I don't think belong in issues
The text was updated successfully, but these errors were encountered:
Discussed in #46
Originally posted by JustSimplyKyle May 5, 2022
Warning this is going to be cursed
gh run download -R 'https://github.com/Fabricators-of-Create/Create' $(gh run list -R 'https://github.com/Fabricators-of-Create/Create' -b mc1.18/fabric/dev -w build -L 1 --json databaseId --jq '.[0].databaseId')
using this command, you can download Create's action articifact.
The requirement for other similar are
https://github.com/Fabricators-of-Create/Create
mc1.18/fabric/dev
build
And this should work!
(But create has two files in
Artificats
, one source, and another one normal. This would also require Implement filtering for GitHub releases. #29to be implemented. Or else it would probably use the wrong file)
Although the use of
gh
is not that good here. It should technically be possible to do this via pure curl, but I'm not that good at it.And for upgrading action files, I got an idea.
Save the current commit hash(not the actual file hash, but the github commit hash)
And if the current commit hash doesn't equal to upstream's commit hash, update.
I put this feature in discussions because it's such a strange feature and strange solution that I don't think belong in issues
The text was updated successfully, but these errors were encountered: