How to use multiple GIT accounts per folder on Linux

Tom Benevides — Mon, 22 Feb 2021 04:12:39 +0000

Tipically, one of the first tools that a developer learns when starting the "dev journey" is git. For those who still don't know much about this little guy, it was created by Linus Benedict Torvalds, a Finnish software engineer, naturalized American, known as the creator of linux kernel. Torvald's idea was to have a simple versioning system that met three requirements that he himself considered indispensable (and that other software couldn't guarantee):

It needed to be distributed;
The performance had to be good;
It needed to ensure that what was put in, was exactly what was obtained afterwards;

According to him, these three parameters were sufficient to discard virtually all versioning systems until then, so he decided to build his own system.

A single git account on Linux: kid's stuff

Everyone who has ever set up a local git user knows that it have no secrets. You define the user name and email and... that's it.

git config --global user.name "Tom Benevides"
git config --global user.email "tombenevides@mail.com"

From now on, all the repositories you create will use these credentials.

mkdir new_repo && cd "$_"
git init
touch text.txt
git add text.txt
git commit -m "new file"

And if I take a look at the git log, this will be the result:

commit 036573401e5788917383a27fb6c2acf607f5e441 (HEAD -> master)
Author: Tom Benevides <tombenevides@mail.com>
Date:   Sun Feb 7 13:50:05 2021 -0400

   new file

So, everything is fine with our configuration but... what if my project uses a different account?

A git account per repository: still piece of cake, but it can be a little tricky

We'll now create another repository. This is going to be the work_repo. It actually uses a different email account because it's a company project and not a personal project like new_repo.

cd ~
mkdir work_repo && cd "$_"
git init
touch text.txt

If we commit the changes now, my personal account (system default) will be registered, but I need to use the work email, tombenevides@work.com. So, we need to configure the new credentials in the repository.

git config user.email "tombenevides@work.com"
git add text.txt
git commit -m "new file"

Now, when committing, my registered email will be the work email.

commit f47e5c7140296c9fbe1f4fb001149b04b329b655 (HEAD -> master)
Author: Tom Benevides <tombenevides@work.com>
Date:   Sun Feb 7 14:05:02 2021 -0400

   new file

All right, happy ending? So-so. Now, imagine that you have several work repositories and several personal repositories. It will be a bit annoying that you have to configure the correct credential in each of the repositories. If your work account email changes or you have a new git account? You'll need to make the change in all repositories. Lot of job right? There're people who don't think so.

Personally, what I can do to make my life simpler, I’m doing and a nice idea would be to configure git so that every time I create a repository in a given folder, the credentials I want are automatically assigned to it. And look how cool; git does that!

A git account per folder: the light at the end of the tunnel

The idea is pretty simple: we'll have two base folders (Work and Personal) where the repositories will be stored according to their respective origin. All repositories within each base folder will use the same credentials, different from the default and without configuration by repository. Structure proposal below.

Projects
├── Personal
└── Work

Now, we need to tell git that the Personal folder repositories will use the email "tombenevides@newmail.com" and not the default email we set up earlier. To do this, in your home (cd ~), create a file called .gitconfig-personal and as content, simply recipient of the email.

[user]
  email = tombenevides@newmail.com

Once we set up the Personal folder credential, we will create a .gitconfig-work file to set up work credential.

[user]
  email = tombenevides@work.com

With our config files created, we'll now edit the .gitconfig file found in the user home (cd ~) and let git know that whenever there is a repository inside the Personal folder, it must use the credential of the .gitconfi-personal file and every time there is a repository in the Work folder, git must use the credential of the .gitconfig-work file.

[user]
    name = Tom Benevides
    email = tombenevides@mail.com
[includeIf "gitdir:Projects/Personal/**"]
    path = .gitconfig-personal
[includeIf "gitdir:Projects/Work/**"]
    path = .gitconfig-work

... and voilà! Now, the work repositories only need to be inside the ~/Projects/Work directory and all commits will use the correct credentials, without any configurations by repository. The same goes to the Personal folder repositories. And if at any point, your work (or personal) git account email changes, just change the .gitconfig-X file corresponding to the folder and all repositories inside will use the new credential.

So... that's it! Try it and then tell me your experience in the comments, via Twitter or Instagram!

Add shortcut to VS Code in File Manager on Linux Mint

Tom Benevides — Thu, 05 Dec 2019 02:20:52 +0000

My programming job forces me to improve myself in many skills. One of them is managing multiples projects at the same time. As a web developer at a Brazilian university, I have to do many things to compensate for the low human and financial resources, very common at Brazilian government departments. So, I'm the guy who implements new services, maintain them and research/test new techs that maybe can help us.

So, because of that, I usually have a few instances of my IDE opened for doing such things. Something very annoying (at least for me), is open a project with an IDE. You open your favorite IDE, then go to open project and choose the project folder. Now, imagine doing that 3 or 4 times. Sometimes, I want some agility and this process is not that fast.

Lucky me, I use Linux. So, I can do many things in that OS and customization is one of them (I don't know if I can customize Windows, I just say: I can do it on Linux). Anyway, the idea is very simple:

You just right-click on the project folder you want to open
select the "Open on IDE"
Happy life, easy-peasy.

Tools and Steps

For this "feature", I used an IDE, specifically the Visual Studio Code (aka VS Code) and the Linux Mint Cinnamon OS. I will not argue here about why I use VS Code + Mint and why YOU guys should use it because is not the purpose, now.

Now the big work! Pay attention!

You just need to create a file at ~/.local/share/nemo/actions named open-vscode.nemo_actions and paste this code on it:

[Nemo Action]

Name=Open on VS Code...

Comment=Open a Folder into Visual Studio Code

Exec=<open-vscode.sh %F>

Icon-Name=view-sidetree

Selection=Any

Extensions=dir;


Name[en]=Open on VS Code

This little piece of code is telling us:

[Nemo Action] Name: "Create a command named Open on VS Code"
Exec: "execute this script when someone uses the new command"
Icon: "Show the command option with this icon"
Selection: "Allow the command for this number of selected items"
Extensions: "Allow the command for items with these extensions"
Name[x]: "The message will appear like this in that language"

Besides that, you have to implement the script, who actually makes the magic. So, create at the same folder a file named open-vscode.sh and paste this code on it:

#!/bin/bash


DIR="$(cd "$(dirname "$1")"; pwd -P)/$(basename "$1")"

cd $DIR && code .

This code is even more simple: the first line gets the absolute path of your selected item and the second line flows into your item folder running the VS Code. Now, just run on terminal nemo -q to reload the file manager and.. Ta-da! pom-pom pom-pom \o/.

Oh! Don't forget to give execute permission to the script or none of this will work.

So, that's it. You can add more commands (or actions as Nemo calls) just creating other .nemo_actions files as you wish. These customize commands will work only in your account once they're in your home folder. If you want to make these commands global on your Linux Mint, copy the .nemo_actions file to /usr/share/nemo/actions and then reload the file manager.

If you liked the post, react or comment on it. And don't forget to share with other people who might enjoy this tip. So .. See you soon!