I believe you can do:
git reset HEAD@{1}
To go one commit forward in time. To go forward multiple commits, use HEAD@{2}, HEAD@{3}, etc.
More Related Contents:
- How do I force "git pull" to overwrite local files?
- How do I revert a Git repository to a previous commit?
- Is there a way to cache https credentials for pushing commits?
- How can I see the changes in a Git commit?
- How line ending conversions work with git core.autocrlf between different operating systems
- How do I properly force a Git push?
- Combining multiple git repositories
- Generating statistics from Git repository [closed]
- How do I “git blame” a deleted line?
- How to see the changes between two commits without commits in-between?
- How to use git-bundle for keeping development in sync?
- git move directory to another repository while keeping the history
- git rebase and git push: non-fast forward, why use?
- Git submodule to track remote branch
- Git diff against a stash
- Heroku: How to push different local Git branches to Heroku/master
- How do I rename a repository on GitHub?
- Send a pull request on GitHub for only latest commit
- diff returning entire file for identical files
- Unable to Connect to GitHub.com For Cloning
- How to .gitignore all files/folder in a folder, but not the folder itself? [duplicate]
- What does git rev-parse do?
- What is git actually doing when it says it is “resolving deltas”?
- Update a development team with rewritten Git repo history, removing big files
- “git pull” broken
- What do git checkouts really mean?
- What is the reason for “Procfile declares types -> (none)” in Heroku?
- List of all commands that cause git gc –auto
- Can I include other .gitignore file in a .gitignore file? (like #include in c-like languages)
- When should I use “git push –force-if-includes”