If your remote (BitBucket) allows force-pushing, you can do this:
git reset --hard <last_good_commit_ID> git push -f
You should NOT do that if anyone has pulled down the bad commit, as it will screw up their ability to push back to the repo. Also don't do this if there are any good commits after the bad commit that you don't want to lose.
git revert <bad_commit_ID> git push
will push a commit that reverses the changes made by the bad commit, but it won't remove the bad commit from the repo. This is better if other people have pulled down the bad commit because they will also pull down the commit that reverts it, but this may not accomplish your goal if you want to delete it from the remote repo as if it was never there.
Using normal techniques, you can't. There are surely some advanced commands that might allow you to delete the commit from the repo, but they aren't specific to Bitbucket, so you should probably take your question to a larger Q&A site (stackoverflow, for example) and phrase it as "git" or "mercurial", rather than "bitbucket".
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs