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
Here is the error message:
remote: Personal access tokens (classic) are forbidden from accessing this repository.
fatal: unable to access '': The requested URL returned error: 403
This action was done successfully yesterday (push successful, no error message) but is failing since this morning.
We need to be able to push in order to ensure our sprint completions and ensure demonstrations.
Could it be possible to know if there was a modification of the token policy recently at os-climate organization level ?
What is the process to follow to be able to push again on our repositories?
Thanks & regards,
Pierre-Jean
The text was updated successfully, but these errors were encountered:
sostrades-pjbarjhoux
changed the title
git push/merge commands blocked due to
git push/merge commands blocked due to token error
Dec 13, 2023
sostrades-pjbarjhoux
changed the title
git push/merge commands blocked due to token error
git push/merge commands blocked due to forbiden token
Dec 13, 2023
This may have changed by error when enrolling the OS-Climate organisation for the new fine-grained access tokens, which are the future replacement. Please can you try this again now?
OK, it is working now on my side, thank you! (with both fine-grained and classic token)
Do we have to communicate to our team that fine-grained token will be required in a near future? is there a date for the replacement? we have devops pipelines involving automatic merges with service accounts, it may be necessary for us to anticipate this.
Hi,
We are facing a major issue that prevents us from pushing code on the following repositories:
https://github.com/orgs/os-climate/teams/os-climate-transition-risk-project/repositories
Here is the error message:
remote: Personal access tokens (classic) are forbidden from accessing this repository.
fatal: unable to access '': The requested URL returned error: 403
This action was done successfully yesterday (push successful, no error message) but is failing since this morning.
We need to be able to push in order to ensure our sprint completions and ensure demonstrations.
Could it be possible to know if there was a modification of the token policy recently at os-climate organization level ?
What is the process to follow to be able to push again on our repositories?
Thanks & regards,
Pierre-Jean
The text was updated successfully, but these errors were encountered: