<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Vinayakk Garg on Medium]]></title>
        <description><![CDATA[Stories by Vinayakk Garg on Medium]]></description>
        <link>https://medium.com/@vinayakk.garg99?source=rss-10a0e1e43466------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*b9Ygo7_e1EMMVzewhJi-Vg.jpeg</url>
            <title>Stories by Vinayakk Garg on Medium</title>
            <link>https://medium.com/@vinayakk.garg99?source=rss-10a0e1e43466------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 15:43:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vinayakk.garg99/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What Happens After Your First Pull Request Gets Merged?]]></title>
            <link>https://medium.com/@vinayakk.garg99/what-happens-after-your-first-pull-request-gets-merged-5102f6a79dd5?source=rss-10a0e1e43466------2</link>
            <guid isPermaLink="false">https://medium.com/p/5102f6a79dd5</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[contribution]]></category>
            <category><![CDATA[git]]></category>
            <dc:creator><![CDATA[Vinayakk Garg]]></dc:creator>
            <pubDate>Fri, 29 Mar 2024 20:26:39 GMT</pubDate>
            <atom:updated>2024-03-29T20:32:08.456Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vWtAEb9iMWPbpJ4b" /></figure><p>I just went through the rollercoaster of getting my first PR merged into the huggingface/transformers repository, and oh boy, was it a ride! The moment it got accepted, I was on cloud nine. But then came the question, “What now?” If you’re in the same boat, fret not! Here’s a simple, no-BS guide on getting ready for round two (or three, or four…) of contributions.</p><p>To work on a new issue in the same repository after your previous PR has been merged and you’ve synced your fork with the original repository, you should follow these steps to update your local repository and clean up any old branches. This process involves a few key steps:</p><ol><li>Celebrate Your Contribution!<br>Take a moment to appreciate your work. Maybe do a little dance or treat yourself to something nice. Sharing your success on social media or with your peers can also be fun!</li><li>Consider GitHub’s Prompt to Delete the Branch:<br>After a PR is merged, GitHub often suggests deleting the now-unused branch from your fork. It’s generally a good practice to keep your repository clean by removing branches that are no longer needed. So, go ahead and click that “Delete branch” button on GitHub’s UI.</li><li>Open your terminal and navigate to your local repository directory.</li><li>Fetch the latest changes from the original repository (upstream). Assuming you’ve already configured a remote for the upstream repository, you can fetch the latest changes without merging them:</li></ol><pre>git fetch upstream</pre><ul><li>* Note: If you haven’t added your original remote as upstream, do this:</li></ul><p>a. Check your current remotes to see if upstream is already defined:</p><pre>git remote -v</pre><p>b. Add the original repository as upstream if it’s not already set.</p><pre>git remote add upstream https://github.com/original_owner/original_repository.git</pre><p>5. Switch to your master/main branch.</p><pre>git checkout master<br># or, if the main branch is named &#39;main&#39;<br>git checkout main</pre><p>6. Merge the latest changes from the upstream repository into your local master/main branch.</p><pre>git merge upstream/master<br># or, if the main branch is named &#39;main&#39;<br>git merge upstream/main</pre><p>7. Push the updates to your fork on GitHub. This step ensures that your fork’s master/main branch is up to date with the upstream repository.</p><pre>git push origin master<br># or, if the main branch is named &#39;main&#39;<br>git push origin main</pre><p>8. Delete the old branch related to the previous PR, if you no longer need it. First, make sure you’re not on the branch you want to delete:</p><pre>git branch -d branch-name</pre><p>9. Create a new branch for the new issue you’re working on. It’s a good practice to work on different branches for different issues.</p><pre>git checkout -b &lt;NEW_FEATURE_BRANCH&gt;</pre><p>10. Make sure your new branch is up to date with the upstream repository. This is just a precaution to ensure you’re starting with the latest codebase.</p><pre>git pull upstream master<br># or, if the main branch is named &#39;main&#39;<br>git pull upstream main</pre><p>Now, your local setup is clean and up-to-date, and you’re ready to start working on the new issue in a new branch. Working in this manner helps to keep your contributions organized and makes it easier for maintainers to review your changes.</p><p>Hope all your PRs get merged, Peace ✌🏻</p><p>If you&#39;re yet to make your first contribution, check this out: <a href="https://medium.com/@vinayakk.garg99/no-bs-guide-to-your-first-open-source-contribution-a6e7632e2c9e">https://medium.com/@vinayakk.garg99/no-bs-guide-to-your-first-open-source-contribution-a6e7632e2c9e</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5102f6a79dd5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[No BS guide to your first open-source contribution]]></title>
            <link>https://medium.com/@vinayakk.garg99/no-bs-guide-to-your-first-open-source-contribution-a6e7632e2c9e?source=rss-10a0e1e43466------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6e7632e2c9e</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Vinayakk Garg]]></dc:creator>
            <pubDate>Thu, 28 Mar 2024 23:18:41 GMT</pubDate>
            <atom:updated>2024-03-28T23:27:20.140Z</atom:updated>
            <content:encoded><![CDATA[<h4>This article serves the exact purpose that the title says. So, you’ve figured out the open-source project you want to start contributing to. What’s next?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kH74toLtQFGgx1af" /></figure><h3>Step 1: Fork the repository</h3><ol><li>Navigate to the GitHub page of the project you want to contribute to.</li><li>Click on the “Fork” button at the top right corner. This creates a copy of the repository in your GitHub account.</li></ol><h3>Step 2: Clone your fork</h3><ol><li>Navigate to your fork on GitHub.</li><li>Click the “Code” button and copy the URL for cloning.</li><li>Open your terminal and run:</li></ol><pre>git clone https://github.com/your_username/repository_name.git</pre><p>4. Navigate to the cloned repository on your machine:</p><pre>cd repository_name</pre><h3>Step 3: Configure the remotes:</h3><ol><li>Add the original repository as a remote (this is typically called upstream):</li></ol><pre>git remote add upstream https://github.com/original_owner/repository_name.git</pre><p>2. Verify the new upstream repository you’ve specified for your fork:</p><pre>git remote -v</pre><h3>Step 4: Create a new branch:</h3><ol><li>Create and switch to a new branch on which you will make your changes:</li></ol><pre>git checkout -b &lt;NEW_BRANCH_NAME&gt;</pre><h3>Step 5: Make your changes:</h3><ol><li>Edit or add files in your local repository as needed for your contribution.</li><li>Use git add to stage your changes.</li></ol><pre>git add .</pre><p>3. Commit your changes with a descriptive message:</p><pre>git commit -m &quot;brief description of your changes&quot;</pre><h3>Step 6: Pull the latest changes</h3><p>Before pushing your changes, ensure your branch is up to date with the original project’s main branch:</p><ol><li>Fetch the latest changes from upstream:</li></ol><pre>git fetch upstream</pre><p>2. Merge these changes into your branch (ensure you’re on your branch):</p><pre>git merge upstream/main</pre><p>3. Resolve any merge conflicts that arise and commit your changes.</p><h3>Step 7: Push Changes to Your Fork</h3><p>Push your changes:</p><pre>git push origin &lt;NEW_BRANCH_NAME&gt;</pre><h3>Step 8: Create a Pull Request</h3><ol><li>Navigate to your repository on GitHub.</li><li>You’ll see a “Compare &amp; pull request” button for your branch. Click on it.</li><li>Fill out the PR form at the original repository. Include a clear title and description of your changes (mention issue number if needed).</li><li>Submit the pull request by clicking on the “Create pull request” button.</li></ol><h3>Step 9: Follow Up</h3><ul><li>Monitor your PR for any feedback or requests for changes from the project maintainers.</li><li>Make any requested changes and push them to your branch.</li><li>Engage in the discussion until your PR is either merged or closed.</li></ul><p>May all your PRs get merged, Peace ✌🏻</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6e7632e2c9e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>