<?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>Programming on DA</title><link>https://danieleandreis.eu/categories/programming/</link><description>Recent content in Programming on DA</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 05 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://danieleandreis.eu/categories/programming/index.xml" rel="self" type="application/rss+xml"/><item><title>Managing Multiple Git Remotes</title><link>https://danieleandreis.eu/blog/programming/multiple_git_remote/</link><pubDate>Fri, 05 Jun 2026 00:00:00 +0000</pubDate><guid>https://danieleandreis.eu/blog/programming/multiple_git_remote/</guid><description>&lt;p&gt;When collaborating on open-source projects it is common to work with multiple remotes. Typically:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;upstream&lt;/strong&gt;: the original repository maintained by the project owners&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;origin&lt;/strong&gt;: your personal fork of the repository&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This setup allows you to keep your fork synchronized with the original project while developing and contributing changes.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="configuring-the-remotes"&gt;Configuring the Remotes&lt;/h2&gt;
&lt;p&gt;Suppose you have already forked a project on GitHub.&lt;/p&gt;
&lt;p&gt;Check your current remotes:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;git remote -v
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Example output:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-text" data-lang="text"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;origin git@github.com:your-user/project.git (fetch)
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;origin git@github.com:your-user/project.git (push)
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Add the upstream remote:&lt;/p&gt;</description></item><item><title>Git: Time to Clean Up My Workflow</title><link>https://danieleandreis.eu/blog/programming/revisiting_git/</link><pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate><guid>https://danieleandreis.eu/blog/programming/revisiting_git/</guid><description>&lt;p&gt;I started using version control systems many years ago with Subversion (SVN). Later, I tried other systems such as Bazaar, and finally, like many projects and developers, I moved to Git.&lt;/p&gt;
&lt;p&gt;Now I can say that I have been using Git for several years, mostly as a practical tool to manage my code and keep track of changes. In most cases, especially at work, I use it for projects where I am the only developer, or I access repositories created by other people mainly for testing, not as an active developer.&lt;/p&gt;</description></item></channel></rss>