Run always fails with 404 on updating a gist

[PerchunPak]

I recently setuped push to gist, instead of main repo. However, it's now failing with 404 while pushing the changes.

Firstly I thought that I didn't set correct gist ID, but GET request to API with the same ID returns expected answer.

Logs from workflow, gist in UI, request URL.

[lowlighter]

Hello 👋 !

Yeah it's kind of strange indeed 🤔
The link used seems to be the correct one since it works (at least using a GET request)

Just to be rule out one possibility first, when you changed your workflow, did you also update your personal access token to grant gists scope ? If not it could be that

[PerchunPak]

Yeah, sorry. I maybe forgot to click Save button in settings.

[lowlighter]

No worries, glad it worked 👍
Pretty strange that GitHub chose to send back 404 rather than 403

[spenserblack]

Pretty strange that GitHub chose to send back 404 rather than 403

I'm just guessing, but since gists can be "secret," maybe GitHub wants to pretend that the resource doesn't exist when you don't have access to it.

[PerchunPak]

This gist is public.

[spenserblack]

Could just be a catch-all rule they have. if has_access: normal_response; else: 404.