Skip to content
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

git push/merge commands blocked due to forbiden token #366

Open
sostrades-pjbarjhoux opened this issue Dec 13, 2023 · 2 comments
Open

git push/merge commands blocked due to forbiden token #366

sostrades-pjbarjhoux opened this issue Dec 13, 2023 · 2 comments
Assignees

Comments

@sostrades-pjbarjhoux
Copy link

sostrades-pjbarjhoux commented Dec 13, 2023

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

@sostrades-pjbarjhoux 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 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
@ModeSevenIndustrialSolutions
Copy link
Contributor

ModeSevenIndustrialSolutions commented 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?

@sostrades-pjbarjhoux
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants