<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Commits on Nerdsid.com</title><link>https://nerdsid.com/tags/commits/</link><description>Recent content in Commits on Nerdsid.com</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 11 Dec 2024 07:32:28 +0530</lastBuildDate><atom:link href="https://nerdsid.com/tags/commits/index.xml" rel="self" type="application/rss+xml"/><item><title>Git terms explained in simple words</title><link>https://nerdsid.com/posts/git-terms-explained-in-simple-words/</link><pubDate>Wed, 11 Dec 2024 07:32:28 +0530</pubDate><guid>https://nerdsid.com/posts/git-terms-explained-in-simple-words/</guid><description>&lt;h3 id="branches">Branches&lt;/h3>
&lt;p>Branches are copies of the main project where you can make changes without affecting the production project until you&amp;rsquo;re ready to integrate the changes. They allow developers to work on new features, bug fixes, or experiment in isolation. When the changes are complete and reviewed, you merge the branch back into the main project.&lt;/p>
&lt;p>Examples:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Feature branches&lt;/strong>: Used for developing new features. For example, if you&amp;rsquo;re adding a login page to a website, you would create a feature branch like &lt;code>feature/login-page&lt;/code> to make all the necessary changes.&lt;/li>
&lt;li>&lt;strong>Bugfix branches&lt;/strong>: Created to fix specific bugs. For instance, if there&amp;rsquo;s an issue with the checkout process, a branch like &lt;code>bugfix/checkout-error&lt;/code> could be used.&lt;/li>
&lt;li>&lt;strong>Release branches&lt;/strong>: Prepared when you&amp;rsquo;re close to releasing a version of the project. A release branch might be named &lt;code>release/v1.0&lt;/code> to finalize new features before they go live.&lt;/li>
&lt;li>&lt;strong>Hotfix branches&lt;/strong>: These are for urgent fixes that need to be addressed in production immediately. An example could be &lt;code>hotfix/critical-bug&lt;/code> to address a security vulnerability found after release.&lt;/li>
&lt;/ul>
&lt;h3 id="commit">Commit&lt;/h3>
&lt;p>A commit is a snapshot of the changes made to files in a branch. It records the specific modifications made at a particular point in time, so that developers can track the history of changes and revert to previous versions if necessary. A commit typically includes a message describing what was changed.&lt;/p></description></item><item><title>Edit Last Commit Message in Git</title><link>https://nerdsid.com/posts/git-edit-last-commit-message/</link><pubDate>Wed, 13 Sep 2023 15:39:06 +0530</pubDate><guid>https://nerdsid.com/posts/git-edit-last-commit-message/</guid><description>&lt;h2 id="introduction">Introduction&lt;/h2>
&lt;p>Picture this: you&amp;rsquo;re on a coding spree, rushing to fulfill a project deadline. You&amp;rsquo;ve just committed your changes to Git. All of a sudden, you notice a typo in your last commit message! But don&amp;rsquo;t worry, you have the ability to correct it in the realm of Git.&lt;/p>
&lt;h2 id="modify-the-last-commit-message">Modify the last commit message&lt;/h2>
&lt;p>To update the last commit message in Git, you can use the &lt;code>--amend&lt;/code> option with the &lt;code>git commit&lt;/code> command. The following command illustrates it.&lt;/p></description></item><item><title>How to Fix Common Git Mistakes</title><link>https://nerdsid.com/posts/avoiding-disaster-how-to-fix-common-git-mistakes-like-a-pro/</link><pubDate>Wed, 03 May 2023 05:27:57 +0000</pubDate><guid>https://nerdsid.com/posts/avoiding-disaster-how-to-fix-common-git-mistakes-like-a-pro/</guid><description>&lt;p>Git is a version control system that allows developers to manage and track changes to their codebase over time. It is easy to make mistakes, while working with Git. This can result in confusion, lost effort, and even data loss. In this post, we&amp;rsquo;ll go over some common Git problems and their solutions. Whether you&amp;rsquo;re new to Git or want to enhance your Git skills, these tips will help you become a more efficient and productive developer.&lt;/p></description></item><item><title>View Files Changed in Git Commits</title><link>https://nerdsid.com/posts/view-details-of-files-in-git-commits/</link><pubDate>Thu, 16 Mar 2023 00:00:00 +0530</pubDate><guid>https://nerdsid.com/posts/view-details-of-files-in-git-commits/</guid><description>&lt;h2 id="introduction">Introduction&lt;/h2>
&lt;p>I recently got into a situation, where changes made to a file was committed, but I was not sure which commit captured those changes. So, I wanted to know the files changed in past commits. One of the easiest way to do this is to simply check the history of your repo on GitHub or GitLab etc. But I didn&amp;rsquo;t push my local commits, since I wanted to ensure that things are perfect before I push. I found the following commands to be useful in this regard.&lt;/p></description></item><item><title>How to Edit Multiple Git Commit Messages</title><link>https://nerdsid.com/posts/git-edit-multiple-commit-messages/</link><pubDate>Fri, 16 Sep 2022 00:00:00 +0530</pubDate><guid>https://nerdsid.com/posts/git-edit-multiple-commit-messages/</guid><description>&lt;h2 id="introduction">Introduction&lt;/h2>
&lt;p>I recently got into a situation, where I had to edit multiple git commit messages. I was contributing to a project and had already added my commits. But, I had to change the commit messages to follow the project&amp;rsquo;s commit message guidelines.&lt;/p>
&lt;h2 id="using-git-rebase-to-edit-commit-history">Using git rebase to edit commit history&lt;/h2>
&lt;p>&lt;code>git rebase&lt;/code> is a powerful command that can be used to edit commit history. It can be used to edit commit messages, squash commits, reorder commits, and much more.&lt;/p></description></item><item><title>How to undo a Git Commit in Your Local and Remote Repository</title><link>https://nerdsid.com/posts/undo-a-git-commit-locally-and-remotely/</link><pubDate>Tue, 13 Sep 2022 17:54:30 +0530</pubDate><guid>https://nerdsid.com/posts/undo-a-git-commit-locally-and-remotely/</guid><description>&lt;h2 id="introduction">Introduction&lt;/h2>
&lt;p>It is very common to make mistakes while working on a project. Sometimes, you may have made a commit with the wrong changes. In such cases, you may want to undo the commit and make a new commit with the correct changes. In this post, we will see how to undo a commit in your local and remote repositories.&lt;/p>
&lt;h2 id="undo-a-commit-in-your-local-repository">Undo a commit in your local repository&lt;/h2>
&lt;p>The word &amp;lsquo;undo&amp;rsquo; here means that:&lt;/p></description></item></channel></rss>