How can I delete a commit that I made on GitLab This commit that I made is not the HEAD now If I can t delete it can I edit When it was the HEAD I tried git reset --soft HEAD git reset --soft HEAD 1 git revert HEAD git rebase -i HEAD git rebase -i HEAD 1 git reset --hard HEAD git reset --hard Id-Code I already tried to rebase it but it still stays on the branch Now I just removed it from the HEAD but it is still there There is another command

We ve had similar problem and it was not enough to only remove commit and force push to GitLab It was still available in GitLab interface using url https gitlab example com lt group gt lt project gt commit lt commit hash gt We ve had to remove project from GitLab and recreate it to get rid of this commit in GitLab UI

Supose you have the following scenario 1bd2200 HEAD master another commit d258546 bad commit 0f1efa9 3rd commit bd8aa13 2nd commit 34c4f95 1st commit Where you want to remove d258546 i e bad commit You shall try an interactive rebase to remove it git rebase -i 34c4f95 then your default editor will pop with something like this pick bd8aa13 2nd commit pick 0f1efa9 3rd commit pick d258546 bad commit pick 1bd2200 another commit Rebase 34c4f95 1bd2200 onto 34c4f95 Commands p pick use commit r reword use commit but edit the commit message e edit use commit but stop for amending s squash use commit but meld into previous commit f fixup like squash but discard this commit s log message x exec run command the rest of the line using shell These lines can be re-ordered they are executed from top to bottom If you remove a line here THAT COMMIT WILL BE LOST However if you remove everything the rebase will be aborted Note that empty commits are commented out just remove the line with the commit you want to strip and save exit the editor pick bd8aa13 2nd commit pick 0f1efa9 3rd commit pick 1bd2200 another commit git will proceed to remove this commit from your history leaving something like this mind the hash change in the commits descendant from the removed commit 34fa994 HEAD master another commit 0f1efa9 3rd commit bd8aa13 2nd commit 34c4f95 1st commit Now since I suppose that you already pushed the bad commit to gitlab you ll need to repush your graph to the repository but with the -f option to prevent it from being rejected due to a non fastforwardeable history i e git push -f lt your remote gt lt your branch gt Please be extra careful and make sure that none coworker is already using the history containing the bad commit in their branches Alternative option Instead of rewrite the history you may simply create a new commit which negates the changes introduced by your bad commit to do this just type git revert lt your bad commit hash gt This option is maybe not as clean but is far more safe in case you are not fully aware of what are you doing with an interactive rebase

[git] Delete commit on gitlab

git reset --hard CommitId
git push -f origin master

1st command will rest your head to commitid and 2nd command will delete all commit after that commit id on master branch.

Note: Don't forget to add -f in push otherwise it will be rejected.

Examples related to git

• Does the target directory for a git clone have to match the repo name? • Git fatal: protocol 'https' is not supported • Git is not working after macOS Update (xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools) • git clone: Authentication failed for <URL> • destination path already exists and is not an empty directory • SSL_connect: SSL_ERROR_SYSCALL in connection to github.com:443 • GitLab remote: HTTP Basic: Access denied and fatal Authentication • How can I switch to another branch in git? • VS 2017 Git Local Commit DB.lock error on every commit • How to remove an unpushed outgoing commit in Visual Studio?

Examples related to gitlab

• GitLab remote: HTTP Basic: Access denied and fatal Authentication • How can I switch to another branch in git? • HTTP Basic: Access denied fatal: Authentication failed • Getting permission denied (public key) on gitlab • Delete commit on gitlab • error: RPC failed; curl transfer closed with outstanding read data remaining • ssh : Permission denied (publickey,gssapi-with-mic) • Fix GitLab error: "you are not allowed to push code to protected branches on this project"? • Change Default branch in gitlab • How can I clone a private GitLab repository?