Conversation
.github/workflows/build.yml
Outdated
| artifact=textures-latest | ||
| list_asset_url=https://api.github.com/repos/tribesthatmaybe/art_source/actions/artifacts | ||
| asset_url=$(curl "${list_asset_url}" | jq ".artifacts[] | select(.name==\"${artifact}\") | .url" | sed 's/\"//g')/zip | ||
| wget -O textures-latest.zip $asset_url/zip?access_token=${GITHUB_TOKEN} |
There was a problem hiding this comment.
try using ART_PAT but remember to declare it in the env section
There was a problem hiding this comment.
this pulls down the latest art assets right? we should figure out how to pin it
also been thinking about #85
There was a problem hiding this comment.
Yeah, it's just textures for the time being. Thinking nightly/rolling builds pull latest and tag builds pull that tag from art-source (don't have anything tagged yet, should probably start prerelease tagging at this point), thought just having the tag to use as a variable somewhere works for me just fine.
Also thanks for the declaration reminder :D
|
crap, @otakup0pe looks like I didn't have the correct grant. for some reason my little rinkadink test let this work with read on repo. { |
|
so, somehow I got this thing working here: https://github.com/tribesthatmaybe/artifact_fetch_test/runs/1079679548, giving the PAT only read public. Could it have to do with the user which is associated with the PAT not having some access, best I could tell is the error I got seems to be related to some sort of API scope which is per-user, but I'm not terribly confident in my analysis |
|
showing off my inexperience with github workflows: am I guessing right that you created a github app for this, and not just a PAT for your account? didn't realize that was a thing until now, and in that case I gave you the wrong needed permissions |
2 participants
No description provided.