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
(I'm not sure if this is the correct way to ask about this)
While using this action, I encountered an issue inside a long-living self-hosted runner. I was generating a temporary GitHub app token with the actions/create-github-app-token@v1 action and then using this action to configure my git creds so I could perform some git clone commands on different repositories.
So the issue is that the first time I ran a job similar to the one found below, it worked without issue, but when I retried to run the job a second time it failed with an authentication error. While troubleshooting the runner I noticed that the action keeps the previously saved token on the /git/credentials file (that on this second run, this token was expired by the create-github-app-token post-action step). I solved the issue by removing this file at the beginning of the job, but I wanted to know if we could add an option to this action that removes this file for us (so other folks can avoid this issue).
Hi, community 👋🏽
(I'm not sure if this is the correct way to ask about this)
While using this action, I encountered an issue inside a long-living self-hosted runner. I was generating a temporary GitHub app token with the actions/create-github-app-token@v1 action and then using this action to configure my git creds so I could perform some git clone commands on different repositories.
So the issue is that the first time I ran a job similar to the one found below, it worked without issue, but when I retried to run the job a second time it failed with an authentication error. While troubleshooting the runner I noticed that the action keeps the previously saved token on the /git/credentials file (that on this second run, this token was expired by the create-github-app-token post-action step). I solved the issue by removing this file at the beginning of the job, but I wanted to know if we could add an option to this action that removes this file for us (so other folks can avoid this issue).
The text was updated successfully, but these errors were encountered: