“GIT -Befehlsänderung in vorheriger Komit” Code-Antworten

GIT -Befehlsänderung in vorheriger Komit

git revert --no-commit 0766c053..HEAD
git commit


If you really do want to have individual commits 
(instead of reverting everything with one big commit), 
then you can pass --no-edit instead of --no-commit, 
so that you don't have to edit a commit 
message for each reversion. – user456814
Wrong Wryneck

GIT -Befehlsänderung in vorheriger Komit

git checkout <commit_id>
git checkout -b <new branch> <commit_id>
git checkout HEAD~X // x is the number of commits t go back
Wrong Wryneck

GIT -Befehlsänderung in vorheriger Komit

git reflog
git checkout HEAD@{...}
Wrong Wryneck

GIT -Befehlsänderung in vorheriger Komit

# This will create three separate revert commits:
git revert a867b4af 25eee4ca 0766c053

# It also takes ranges. This will revert the last two commits:
git revert HEAD~2..HEAD

#Similarly, you can revert a range of commits using commit hashes (non inclusive of first hash):
git revert 0d1d7fc..a867b4a

# Reverting a merge commit
git revert -m 1 <merge_commit_sha>

# To get just one, you could use `rebase -i` to squash them afterwards
# Or, you could do it manually (be sure to do this at top level of the repo)
# get your index and work tree into the desired state, without changing HEAD:
git checkout 0d1d7fc32 .

# Then commit. Be sure and write a good message describing what you just did
git commit
Wrong Wryneck

Ähnliche Antworten wie “GIT -Befehlsänderung in vorheriger Komit”

Fragen ähnlich wie “GIT -Befehlsänderung in vorheriger Komit”

Weitere verwandte Antworten zu “GIT -Befehlsänderung in vorheriger Komit” auf Shell/Bash

Durchsuchen Sie beliebte Code-Antworten nach Sprache

Durchsuchen Sie andere Codesprachen