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

Need maintainer access to put back master in a correct state 😇 #341

Closed
johnraz opened this issue May 2, 2024 · 1 comment
Closed

Comments

@johnraz
Copy link
Collaborator

johnraz commented May 2, 2024

I made a mistake today while trying to get some commits that were wrongly put on master on develop (see: #337)

Seems like while resolving conflict it merged develop on master ...

I was abe to revert the change #339 but it made the matter worse as now master things it's ahead of develop and trying to merge develop into master has no effect anymore 🤦

TIL don't trust integrated editor in GH 😇

The easiest way out would be to force push master to the original commit before any merge from develop happened the commit is: 5c128c7787ba703d29a1b28bbe2c45973208fec6 (5c128c7)

Basically doing:

git checkout master
git reset --hard 5c128c7787ba703d29a1b28bbe2c45973208fec6
git push -f origin master

But in order to do that we need to allow force push on master for a little while and I don't have the permissions to do so :/

@giovannicimolin do you have maintainer rights?

I will also try through the jazzband help repo

I also added a message to the readme on master to try to raise awareness of this situation (837b9e4)

Very sorry for the noise 😢

@johnraz
Copy link
Collaborator Author

johnraz commented May 2, 2024

Ok nevermind seems force pushing is allowed - everything should be back in shape 👍

@johnraz johnraz closed this as completed May 2, 2024
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

1 participant