<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Vincent Enebuse</title>
    <description>The latest articles on DEV Community by Vincent Enebuse (@vinceenebuse).</description>
    <link>https://dev.to/vinceenebuse</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2948270%2F7f214cf2-3261-4317-8b67-2e0438a821dc.PNG</url>
      <title>DEV Community: Vincent Enebuse</title>
      <link>https://dev.to/vinceenebuse</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/vinceenebuse"/>
    <language>en</language>
    <item>
      <title>My Git Musings</title>
      <dc:creator>Vincent Enebuse</dc:creator>
      <pubDate>Sat, 07 Feb 2026 15:50:05 +0000</pubDate>
      <link>https://dev.to/vinceenebuse/my-git-musings-506b</link>
      <guid>https://dev.to/vinceenebuse/my-git-musings-506b</guid>
      <description>&lt;p&gt;Git as a Version Control tool has become ubiquitous and it's use and importance in the DevOps space cannot be overemphasized considering that it is used for versioning&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Configuration files and scripts (IaC),&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Storing and collaborating on Automation scripts, and also for&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Triggering build automation (CI/CD pipelines).&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Git's wide usage in the DevOps space has led to the concept of GitOps where it serves as the single source of truth for both application code and environment configurations. &lt;/p&gt;

&lt;p&gt;After spending a few days studying Git and it's usage I decided to write a few things (best practices and tips) that I want to remember. &lt;/p&gt;

&lt;p&gt;&amp;nbsp;&lt;/p&gt;

&lt;h3&gt;
  
  
  Tips and Best Practices
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Use the &lt;code&gt;git config&lt;/code&gt; command to adequately configure your commit authorship.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;It is important to use meaningful and descriptive commit messages.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Commit small chunks and only related work as it makes it easier to review/audit your work.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Pull often from your remote git repo using &lt;code&gt;git pull --rebase&lt;/code&gt; to keep your branch up to date and possibly avoid merge conflicts. &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Use &lt;code&gt;git reset&lt;/code&gt; mainly to reverse local changes. &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Use &lt;code&gt;git revert&lt;/code&gt; to reverse changes that have been merged to your remote git repo. &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Create and use a new branch for a new feature or bugfix and name the branch with the prefix feature/* and bugfix/* respectively.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Thank you for reading and please feel free to ask questions or share other useful tips in the comment section.&lt;/p&gt;

</description>
      <category>git</category>
      <category>github</category>
      <category>programming</category>
      <category>devops</category>
    </item>
  </channel>
</rss>
