One of the GitHub actions broke today because Joe's .env has his updated personal GH_LIMITED_PERSONAL_ACCESS_TOKEN, but Siggie does not have it, and this resulted in an error.
Possible solution
I'm not sure there is a good solution for this. We either have to share personal access tokens from one dev's account and give to other devs. Or each dev has to keep their tokens up-to-date. See 'background'.
Background
Unfortunately, GitHub hasn't yet come out yet with a way to create access tokens for a repository. They have to be tied to a user's account. I have a link to the issue somewhere; it's a feature request issue in GitHub that I've been following for a while now.
Where this is being used: When the refresh is finished, if there are any fetch failure cases, it will call a separate action for that. And it needs a token to do that.
Overview
One of the GitHub actions broke today because Joe's
.envhas his updated personalGH_LIMITED_PERSONAL_ACCESS_TOKEN, but Siggie does not have it, and this resulted in an error.Possible solution
I'm not sure there is a good solution for this. We either have to share personal access tokens from one dev's account and give to other devs. Or each dev has to keep their tokens up-to-date. See 'background'.
Background
Unfortunately, GitHub hasn't yet come out yet with a way to create access tokens for a repository. They have to be tied to a user's account. I have a link to the issue somewhere; it's a feature request issue in GitHub that I've been following for a while now.
Where this is being used: When the refresh is finished, if there are any fetch failure cases, it will call a separate action for that. And it needs a token to do that.