TLDR: Create a separate <code>.gitconfig</code> file to be used when you&#39;re inside a specific folder.
<hr>
<h2 id="problem">Problem</h2>
Let&#39;s say you start in a new job and will use the same computer for developing personal and work projects. The company might request that you set the corporate e-mail on you git config for work commits, which would be done like this:
<pre><code class="language-bash">$ git config --global user.email &quot;email@company.com&quot;
</code></pre>
Although simple, this solution would cause the commits on your personal projects to be sent with the corporate e-mail as well, which is not ideal. Here&#39;s the solution I found after going through this recently.
<h2 id="solution">Solution</h2>
As I had never faced this issue before, my first thought was: &quot;Is there a way to set different git user infos depending on the folder I&#39;m in?&quot;. This came to mind because I had already created such folder to keep work files separate from personal stuff, like <code>~/company/git/some_cloned_repo</code>. So, the search I did on Google for that was <a href="https://www.google.com/search?q=per+folder+gitconfig">&quot;per folder gitconfig&quot;</a>, for which the first result was this <a href="https://stackoverflow.com/questions/8801729/is-it-possible-to-have-different-git-configuration-for-different-projects">Stack Overflow question</a>.
You might check that there&#39;s a <code>~/.gitconfig</code> file that looks something like this:
<pre><code># This is Git&#x27;s per-user configuration file.
[user]
# Please adapt and uncomment the following lines:
 name = Your name
 email = personal@email.com
[init]
 defaultBranch = main
</code></pre>
The solution is, given that you have a folder in which all work content is gonna be:
<ol>
<li>Create a new git config file specific to your work, like <code>~/.gitconfig-company</code>:
<pre><code>[user]
 name = Your name
 email = email@company.com
</code></pre>
</li>
<li>Append the following lines to the end of the original git config file, <code>~/.gitconfig</code>:
<pre><code>[includeIf &quot;gitdir:~/company/&quot;]
 path = .gitconfig-company
</code></pre>
</li>
</ol>
Now you can check if it&#39;s working by typing the <code>git config user.email</code> command. It should print:
<ol>
<li><code>email@company.com</code> if run inside the <code>~/company</code> folder and subfolders;</li>
<li><code>personal@email.com</code> if run outside the <code>~/company</code> folder;</li>
</ol>
<h2 id="references">References</h2>
<ul>
<li><a target="_blank" rel="noopener" href="https://stackoverflow.com/questions/8801729/is-it-possible-to-have-different-git-configuration-for-different-projects">Stack Overflow question</a>;</li>
</ul>

Commit with different git username or email depending on the folder you're in!

How to use different git profiles by folder

TLDR: Use <code>pyenv</code> and <code>pyev-virtualenv</code> in a <code>makefile</code> to quickly set up the Python environment on your projects.
<hr>
<h2 id="problem">Problem</h2>
When you interact with multiple projects it becomes difficult to manually manage each one of their required environments. In this article we&#39;ll go through a way that I particularly like to deal with this issue, and you might like it too.
To make things clear, imagine you&#39;re working on two Python projects, each with its own dependency requirements. Let&#39;s say that <code>my-first-project</code> has <code>Flask</code> and <code>SQLAlchemy</code> as dependencies, while <code>my-second-project</code> depends on <code>FastAPI</code> and <code>pymongo</code>.
Installing all of these dependencies to the global environment on your computer might work just fine, although it&#39;s <a target="_blank" rel="noopener" href="https://stackoverflow.com/a/41972262/9234095">not recommended</a>. What we could do to ensure each project has its own dependencies separate from the global environment is use a <a target="_blank" rel="noopener" href="https://docs.python.org/3/library/venv.html">virtualenv</a> for each one.
Another problem that becomes common with time is that each project may depend on a specific Python version. This is something that <code>virtualenv</code> itself cannot solve, but <a target="_blank" rel="noopener" href="https://github.com/pyenv/pyenv">pyenv</a> does! It allows us to install and select any Python version that we need.
<h2 id="solution">Solution</h2>
Once its <a target="_blank" rel="noopener" href="https://github.com/pyenv/pyenv#installation">installed</a>, <code>pyenv</code> can be used to:
<ol>
<li>Install a specific Python version;</li>
<li>Create a <code>virtualenv</code> specifically with that version;</li>
<li>Activate the <code>virtualenv</code> to safely start installing dependencies;</li>
</ol>
Step three should be done within the project folder. The commands would look like this, respectively:
<pre><code class="language-bash">pyenv install 3.10.0
pyenv virtualenv 3.10.0 my-first-project
cd my-first-project
pyenv local my-first-project
</code></pre>
These commands are enough to ensure that you&#39;ll be working on the optimal environment for that project, regarding Python version. But when it comes to dependency management, one common pattern is to specify them in a <code>requirements.txt</code> file. Considering this approach, the following steps could be used:
<ol>
<li>Uninstall all currently installed dependencies;</li>
<li>Update <code>pip</code>&#39;s version;</li>
<li>Install the dependencies specified in <code>requirements.txt</code>;</li>
</ol>
Again, the commands would look like this:
<pre><code class="language-bash">cd my-first-project
pip freeze | xargs -r pip uninstall -y
python -m pip install --upgrade pip
pip install -r requirements.txt
</code></pre>
The three steps above allows us to safely reset the dependencies installed in the current <code>virtualenv</code> without having to recreate it completely.
As remembering these can become annoying after a while, we could use the help of a <a target="_blank" rel="noopener" href="https://opensource.com/article/18/8/what-how-makefile">makefile</a>. Create a <code>makefile</code> in the root folder of your project and insert the following lines:
<pre><code class="language-makefile">.PHONY: environment
environment:
 pyenv install -s 3.10.0
 pyenv uninstall --force my-project
 pyenv virtualenv 3.10.0 --force my-project
 pyenv local my-project

.PHONY: install
install:
 pip freeze | xargs -r pip uninstall -y
 python -m pip install --upgrade pip
 pip install -r requirements.txt
</code></pre>
Now all you have to do is run <code>make environment</code> and then <code>make install</code> to have a fresh Python environment with all its dependencies properly isolated from the rest of your system. Bumped a dependency version? Running only <code>make install</code> should be enough.
<h2 id="references">References</h2>
<ul>
<li>This Wikipedia <a target="_blank" rel="noopener" href="https://en.wikipedia.org/wiki/Xargs">article</a> explains <code>xargs</code>;</li>
</ul>

Work with multiple projects in a safe way!

How to setup your Python environment

TLDR: Running this command on the terminal will delete all local branches except for master and main in the current git repository:
<pre><code class="language-bash">git branch | grep -Ev &quot;(master|main)$&quot; | xargs git branch -D
</code></pre>
<hr>
<h2 id="problem">Problem</h2>
After working for some time on a project you probably end up with several old branches, each created for a different task, right? Have you noticed how many of these do you have on your local repos right now?
The first time I noticed this issue was about a year into my job, when I tried to create a new branch such as <code>bump-dependencies</code> for a quick chore and got an error message because it already existed. It took me some time to remember that I had done the same thing some time ago on that repo, and that&#39;s why branch was still there even though it was merged to the remote for a while.
It&#39;s ok to solve this problem with a simple <code>git branch -D old-branch</code> when there&#39;s only one or even a few branches left over, but it gets boring to do so for several branches on each repo you have local. So, the solution is to come up with a single command that will do it all at once for the current repo. You&#39;ll still have to run it on each repo, but it&#39;s still better than the alternative, isn&#39;t it?
<h2 id="solution">Solution</h2>
To write the solution we&#39;ll start with a <code>git branch</code> command that returns all existing local branches for the current git repo, then we&#39;ll pipe its output to the input of a <code>grep -Ev &quot;(master|main)$&quot;</code> that filters either the <code>main</code> or <code>master</code> branch and returns all others. Finally, that second output is piped into a <code>xargs git branch -D</code> that maps each branch name to a <code>git branch -D</code> command, thus deleting it. So, the full command is:
<pre><code class="language-bash">git branch | grep -Ev &quot;(master|main)$&quot; | xargs git branch -D
</code></pre>
Be careful to use this command when you&#39;re finished working on all local branches or at least they&#39;re all pushed to remote, otherwise you might lose precious work that&#39;s still only local!
You can also create an alias to avoid having to remember the whole command all the time, although it&#39;s not an issue if you have the finder enabled on your terminal:
Add the following line to your <code>.bashrc</code> or <code>.zshrc</code> file:
<pre><code class="language-bash">alias gclear=&#x27;git branch | grep -Ev &quot;(master|main)$&quot; | xargs git branch -D&#x27;
</code></pre>
<h2 id="references">References</h2>
<ul>
<li>This and other solutions are available on <a target="_blank" rel="noopener" href="https://stackoverflow.com/questions/10610327/delete-all-local-git-branches">Stack Overflow</a>;</li>
<li>This Digital Ocean <a target="_blank" rel="noopener" href="https://www.digitalocean.com/community/tutorials/using-grep-regular-expressions-to-search-for-text-patterns-in-linux">tutorial</a> shows how to use <code>grep</code> with its options;</li>
<li>This Wikipedia <a target="_blank" rel="noopener" href="https://en.wikipedia.org/wiki/Xargs">article</a> explains <code>xargs</code>;</li>
</ul>

Clean up your local git environment with one command!

How to delete all git branches but main

Hi! I&#39;m Luiz Lima, a software engineer from Brazil.
This is my personal website, in which you&#39;ll find my blog posts.
If you wish to know more about my career, let&#39;s connect on <a target="_blank" rel="noopener" href="https://www.linkedin.com/in/umluizlima/?locale=en_US">LinkedIn</a>, or check out my projects on <a target="_blank" rel="noopener" href="https://github.com/umluizlima">GitHub</a>. I&#39;m also on <a target="_blank" rel="noopener" href="https://twitter.com/umluizlima">Twitter</a>.

Blog