<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Github on Suyog Garg</title>
    <link>https://suyoggarg.com/tags/github/</link>
    <description>Recent content in Github on Suyog Garg</description>
    <image>
      <title>Suyog Garg</title>
      <url>https://suyoggarg.com/</url>
      <link>https://suyoggarg.com/</link>
    </image>
    <generator>Hugo -- 0.128.0</generator>
    <language>en</language>
    <copyright>Suyog Garg</copyright>
    <lastBuildDate>Tue, 16 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://suyoggarg.com/tags/github/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Version control with `git` tags</title>
      <link>https://suyoggarg.com/en/posts/2026-06-16-git-tags/</link>
      <pubDate>Tue, 16 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://suyoggarg.com/en/posts/2026-06-16-git-tags/</guid>
      <description>Disclaimer: Based on Google Gemini-Pro prompts!
Managing version numbers can get messy when working solo. If you accidentally created development branches named after version numbers (like v0.1.0) or mixed up your tag formats, you can easily clean up your history and establish a friction-free release workflow.
The Goal Convert version branches into permanent Git tags, format historical versions cleanly (v0.0.1 instead of v0.1), and establish a streamlined process for future releases.</description>
    </item>
  </channel>
</rss>
