-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Github token gives bad credentials #627
Comments
Any idea what I need to do? I see GH_TOKEN in the repository security settings, but it hasn't changed that I'm aware of. |
I'm not sure, but aren't tokens expiring? Maybe just create a new one and set it? |
@razzeee I updated the EMAIL and GH_TOKEN with newly generated values. |
Thank you |
@rectifyer can you check if that token has |
Yeah, the name mismatching like that would be a problem |
@razzeee I believe the GITHUB_TOKEN is automatically created, so you should be able to just use it. |
@razzeee I've never actually used actions before. I re-ran it with debug logging and the 403 seems related to POSTing to one of the xbmc repos.
Here is what I ended up doing:
Hopefully that did what it is supposed to do. I'm not quite sure if it will just work when you tag a new release, or if you need to create your own token and I need to use that in the script.trakt repo. |
Thanks, glad it finally worked |
I guess it still doesn't work? https://github.com/trakt/script.trakt/actions/runs/9238071115/job/25415742582 |
Looking at it again, it start to feel like GITHUB_TOKEN vs GH_TOKEN was done deliberately. And we shouldn't have changed it. Probably used to have a fixed user/token and not a changing one based on who releases. We probably need to fork https://github.com/xbmc/repo-scripts/ with the trakt org for the script to work. https://github.com/trakt/script.trakt/actions/runs/9330076737/job/25683262621 |
Hey @rectifyer can you check the github tokens used for https://github.com/trakt/script.trakt/actions/runs/6113115321/job/16591958743
They might be outdated/expired
The text was updated successfully, but these errors were encountered: