Skip to main content

Five clear and effective ways to revert the last commit

Reverting a commit in Git is a common task, and understanding the different methods can save developers a lot of headaches. Here are five clear and effective ways to revert the last commit:

  1. Using git reset (Soft Reset):

    • This method allows you to move the HEAD pointer to a previous commit without losing your changes.
    • Execute: git reset --soft HEAD~1
    • Explanation:
      • --soft keeps your changes in the working directory.
      • HEAD~1 refers to the commit before the current one.
  2. Using git reset (Hard Reset):

    • Be cautious with this one, as it discards uncommitted changes.
    • Execute: git reset --hard HEAD~1
    • Explanation:
      • --hard resets both the HEAD and the working directory.
      • Again, HEAD~1 points to the previous commit.
  3. Using git revert:

    • Creates a new commit that undoes the changes introduced by a specific commit.
    • Execute: git revert <commit_to_revert>
    • Find the commit ID using git log.
  4. Rollback with git reflog:

    • If you accidentally reset too far, git reflog can save you.
    • Use git reflog to find the commit you want to revert to.
    • Then execute: git reset --hard <commit_id>.
  5. Reverting a Pushed Commit:

    • If the commit has already been pushed to a shared repository, use git revert.
    • It creates a new commit that undoes the changes without overwriting history.
    • Execute: git revert <commit_to_revert>


Popular posts from this blog

Functional Programming in Scala for Working Class OOP Java Programmers - Part 1

Introduction Have you ever been to a scala conf and told yourself "I have no idea what this guy talks about?" did you look nervously around and see all people smiling saying "yeah that's obvious " only to get you even more nervous? . If so this post is for you, otherwise just skip it, you already know fp in scala ;) This post is optimistic, although I'm going to say functional programming in scala is not easy, our target is to understand it, so bare with me. Let's face the truth functional programmin in scala is difficult if is difficult if you are just another working class programmer coming mainly from java background. If you came from haskell background then hell it's easy. If you come from heavy math background then hell yes it's easy. But if you are a standard working class java backend engineer with previous OOP design background then hell yeah it's difficult. Scala and Design Patterns An interesting point of view on scala, is

Alternatives to Using UUIDs

  Alternatives to Using UUIDs UUIDs are valuable for several reasons: Global Uniqueness : UUIDs are designed to be globally unique across systems, ensuring that no two identifiers collide unintentionally. This property is crucial for distributed systems, databases, and scenarios where data needs to be uniquely identified regardless of location or time. Standardization : UUIDs adhere to well-defined formats (such as UUIDv4) and are widely supported by various programming languages and platforms. This consistency simplifies interoperability and data exchange. High Collision Resistance : The probability of generating duplicate UUIDs is extremely low due to the combination of timestamp, random bits, and other factors. This collision resistance is essential for avoiding data corruption. However, there are situations where UUIDs may not be the optimal choice: Length and Readability : UUIDs are lengthy (typically 36 characters in their canonical form) and may not be human-readable. In URLs,

Dev OnCall Patterns

Introduction Being On-Call is not easy. So does writing software. Being On-Call is not just a magic solution, anyone who has been On-Call can tell you that, it's a stressful, you could be woken up at the middle of the night, and be undress stress, there are way's to mitigate that. White having software developers as On-Calls has its benefits, in order to preserve the benefits you should take special measurements in order to mitigate the stress and lack of sleep missing work-life balance that comes along with it. Many software developers can tell you that even if they were not being contacted the thought of being available 24/7 had its toll on them. But on the contrary a software developer who is an On-Call's gains many insights into troubleshooting, responsibility and deeper understanding of the code that he and his peers wrote. Being an On-Call all has become a natural part of software development. Please note I do not call software development software engineering b