<?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>Git on Technical Notes</title><link>http://luispa.com/en/tags/git/</link><description>Recent content in Git on Technical Notes</description><generator>Hugo -- 0.148.0</generator><language>en-US</language><lastBuildDate>Fri, 03 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="http://luispa.com/en/tags/git/index.xml" rel="self" type="application/rss+xml"/><item><title>Gitbox, multiple Git accounts without conflicts</title><link>http://luispa.com/en/posts/2026-04-03-gitbox/</link><pubDate>Fri, 03 Apr 2026 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2026-04-03-gitbox/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-gitbox.svg" alt="Gitbox Logo" width="150px" height="150px" style="float:left; padding-right:25px" />
&lt;p>If you use AI agents or do &lt;em>vibe coding&lt;/em>, you know how quickly repositories pile up across different accounts and providers. Personal GitHub, work GitHub, or even a self-hosted server like Forgejo&amp;hellip; and suddenly you have dozens of repos cloned with the wrong identity, crossed credentials, and a monumental mess.&lt;/p>
&lt;p>This happened to someone very close to me — a non-technical person who is creating many &amp;ldquo;projects&amp;rdquo; with agentic AI and, like anyone starting with Git for versioning and backups, was going crazy.&lt;/p>
&lt;p>I created &lt;strong>&lt;a href="https://github.com/LuisPalacios/gitbox">Gitbox&lt;/a>&lt;/strong> to help &amp;ldquo;non-developers&amp;rdquo; manage multiple accounts and clones more easily, without them stepping on each other. If you&amp;rsquo;re a developer, think of it as another alternative — and if you like it, go ahead. I use it on all my desktops and headless machines.&lt;/p>
&lt;br clear="left"/></description></item><item><title>CRLF vs LF</title><link>http://luispa.com/en/posts/2024-09-28-crlf-vs-lf/</link><pubDate>Sat, 28 Sep 2024 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2024-09-28-crlf-vs-lf/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-crlf.svg" alt="CRLF Logo" width="150px" style="float:left; padding-right:25px" />
&lt;p>When working in software development, one of the most subtle yet crucial aspects you need to be aware of is the difference between line endings in text files between Windows (CRLF &lt;code>\r\n&lt;/code>) and Linux/MacOS (LF &lt;code>\n&lt;/code>).&lt;/p>
&lt;p>This small detail can cause big problems if not handled correctly, especially when working in mixed environments &amp;ndash; &lt;strong>version control conflicts&lt;/strong>, &lt;strong>script incompatibilities&lt;/strong>, &lt;strong>compilation or execution issues&lt;/strong>. I wrote this post to have a handy reference for dealing with this topic, including a few tricks.&lt;/p>
&lt;br clear="left"/></description></item><item><title>Git Multi-Account</title><link>http://luispa.com/en/posts/2024-09-21-git-multicuenta/</link><pubDate>Sat, 21 Sep 2024 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2024-09-21-git-multicuenta/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-git-multi.svg" alt="GIT multi-account Logo" width="150px" style="float:left; padding-right:25px" />
&lt;p>This post will walk you through the process of setting up and using multiple accounts with one or more Git providers (GitHub, GitLab, Gitea). I describe the two options I recommend: &lt;strong>HTTPS + Git Credential Manager&lt;/strong> and &lt;strong>SSH multi-account&lt;/strong>.&lt;/p>
&lt;p>The first, HTTPS + Git Credential Manager, is the one I use most, because it&amp;rsquo;s compatible with CLI and/or GUI tools like Visual Studio, VSCode, Git Desktop, Gitkraken, etc. The second option, SSH multi-account, I delegate to &amp;ldquo;headless&amp;rdquo; machines, servers I connect to remotely via CLI or VSCode remote that need to clone repositories and work on them.&lt;/p>
&lt;br clear="left"/></description></item><item><title>Windows for Development</title><link>http://luispa.com/en/posts/2024-08-25-win-desarrollo/</link><pubDate>Sun, 25 Aug 2024 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2024-08-25-win-desarrollo/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-win-desarrollo.svg" alt="Windows for development logo" width="150px" height="150px" style="float:left; padding-right:25px" />
&lt;p>In this post I describe the steps to set up a Windows 11 machine as a development workstation for a cross-platform environment — Linux, macOS, and Windows. This is not oriented towards &lt;em>Microsoft/Windows-only&lt;/em> software development, but rather for those who like to develop on and for multiple platforms and environments.&lt;/p>
&lt;p>I start from a clean Windows installation (in English), with nothing installed. I took advantage of needing to set up a &lt;a href="http://luispa.com/en/posts/2024-08-23-dual-linux-win/">dual boot&lt;/a> and configured the operating system in a &lt;a href="http://luispa.com/en/posts/2024-08-24-win-decente-obsoleto/">lightweight&lt;/a> manner. The post starts with the CLI and WSL2, and in the second part I cover the tools and programming languages.&lt;/p>
&lt;br clear="left"/>
&lt;style>
table {
font-size: 0.8em;
}
&lt;/style></description></item><item><title>Linux for Development</title><link>http://luispa.com/en/posts/2024-07-25-linux-desarrollo/</link><pubDate>Thu, 25 Jul 2024 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2024-07-25-linux-desarrollo/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-linux-desarrollo.svg" alt="linux development logo" width="150px" height="150px" style="float:left; padding-right:25px" />
&lt;p>In this post I describe my configuration log for setting up a Linux (Ubuntu) machine as a development workstation. I install several graphical and command-line applications that are essential for my workflow.&lt;/p>
&lt;p>Starting from a fresh Ubuntu installation, the installation order can be varied, but I recommend (if your Ubuntu is freshly installed) that you follow the same order to see the same results.&lt;/p>
&lt;br clear="left"/></description></item><item><title>MAC for Development</title><link>http://luispa.com/en/posts/2023-04-15-mac-desarrollo/</link><pubDate>Sat, 15 Apr 2023 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2023-04-15-mac-desarrollo/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-mac-desarrollo.svg" alt="mac development logo" width="150px" height="150px" style="float:left; padding-right:25px" />
&lt;p>In this post I describe my configuration log for setting up a Mac (INTEL or ARM) as a development machine. I install several graphical and command-line applications that are important for using a Mac as a development workstation.&lt;/p>
&lt;p>The installation order can be varied, but this is what I recommend starting from a fresh macOS installation.&lt;/p>
&lt;br clear="left"/></description></item><item><title>Eclipse + Java on a Git Repository</title><link>http://luispa.com/en/posts/2022-10-27-quidomi/</link><pubDate>Sun, 27 Nov 2022 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2022-10-27-quidomi/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-eclipse-gitea.svg" alt="QuiDomi logo" width="150px" style="float:left; padding-right:25px" />
&lt;p>Every now and then I get the urge to practice my rusty Java skills. I&amp;rsquo;m going to write a small program to monitor devices on my home network using Java and SNMP. I like to keep my development projects on my private git server (based on &lt;code>gitea&lt;/code>). In this post I describe the process of creating a git repository, a Java Project with Eclipse, and how to connect them together. If you use GitHub, the process is identical, although the UI options may look slightly different compared to Gitea.&lt;/p>
&lt;br clear="left"/></description></item><item><title>Gitea and Traefik on Docker</title><link>http://luispa.com/en/posts/2022-04-03-gitea-docker/</link><pubDate>Sun, 03 Apr 2022 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2022-04-03-gitea-docker/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-gitea-docker.svg" alt="Gitea traefik docker logo" width="150px" style="float:left; padding-right:25px" />
&lt;p>In this post I describe the installation of &lt;a href="http://gitea.io">Gitea&lt;/a> (GIT server) and &lt;a href="https://doc.traefik.io/traefik/">Traefik&lt;/a> (LetsEncrypt SSL certificate termination), along with &lt;a href="https://redis.io">Redis&lt;/a> (cache) and &lt;a href="https://www.mysql.com">MySQL&lt;/a> (DB). I install all applications as Docker containers on an Alpine Linux running as a virtual machine on my KVM server. In the previous post I explained what Gitea is and how to &lt;a href="http://luispa.com/en/posts/2022-03-26-gitea-vm/">set it up directly on a virtual machine&lt;/a> (without Docker).&lt;/p>
&lt;br clear="left"/></description></item><item><title>Gitea on a VM</title><link>http://luispa.com/en/posts/2022-03-26-gitea-vm/</link><pubDate>Sat, 26 Mar 2022 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2022-03-26-gitea-vm/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-gitea-vm.svg" alt="GIT Logo" width="150px" style="float:left; padding-right:25px" />
&lt;p>&lt;a href="https://git-scm.com">GIT&lt;/a> is a distributed version control system, and we all know the famous centralization services &lt;a href="https://github.com">GitHub&lt;/a> and &lt;a href="https://about.gitlab.com">GitLab&lt;/a>. I recently came across a promising alternative called &lt;strong>&lt;a href="http://gitea.io">Gitea - Git with a cup of tea&lt;/a>&lt;/strong> and decided to install it on a virtual machine.&lt;/p>
&lt;br clear="left"/></description></item><item><title>Git Cheat Sheet</title><link>http://luispa.com/en/posts/2021-10-10-git-cheatsheet/</link><pubDate>Sun, 10 Oct 2021 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2021-10-10-git-cheatsheet/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-git-cheatsheet.svg" alt="GIT Cheatsheet Logo" width="150px" style="float:left; padding-right:25px" />
&lt;p>This post contains &lt;strong>my GIT cheat sheet&lt;/strong>, various reminders I use as a programmer — common commands or situations. It comes in handy for example when I accidentally delete a file and want to recover it, check a previous version of code, or ignore a modification in a specific file.&lt;/p>
&lt;br clear="left"/></description></item><item><title>GIT in Detail</title><link>http://luispa.com/en/posts/2021-04-17-git-en-detalle/</link><pubDate>Sat, 17 Apr 2021 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2021-04-17-git-en-detalle/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-git.svg" alt="Logo GIT" width="150px" style="float:left; padding-right:25px" />
&lt;p>&lt;a href="https://git-scm.com">GIT&lt;/a> is a distributed, free and open-source version control system, designed to handle everything from small to very large projects with speed and efficiency. It does not depend on a central repository; multiple users can install GIT and communicate with each other without going through a central server. The thing is that would be unmanageable, so &amp;ldquo;central (remote) servers or repositories&amp;rdquo; are very useful and necessary, &lt;strong>the most famous being &lt;a href="https://github.com">GitHub&lt;/a>, &lt;a href="https://about.gitlab.com">GitLab&lt;/a> and &lt;a href="https://gitea.io/en-us/">Gitea&lt;/a>&lt;/strong>.&lt;/p>
&lt;br clear="left"/></description></item></channel></rss>