• Personal GitHub account

• Office / company Git account

At first this caused a lot of small problems.

Sometimes I would commit to a personal project and later notice that the commit author was my office email.

Other times a company repository showed my personal email in the commit history.

This happens because Git uses the same global identity everywhere unless we configure it differently.

So I created a clean setup where Git automatically switches identity depending on the folder.

The result:

✔ No manual switching
✔ No wrong commit emails
✔ Clean project organization
✔ Works automatically

This guide shows the exact setup you can copy-paste and use.

The Idea

We will organize projects like this:

~/workspace
   ├── personal
   └── work

Git behavior:

This way Git automatically chooses the correct identity.

Step 1 — Create Workspace Folders

Run this:

mkdir -p ~/workspace/personal
mkdir -p ~/workspace/work

Your structure becomes:

workspace
 ├── personal
 └── work

Step 2 — Create Personal Git Config

Create a separate Git config file for your personal identity.

nano ~/.gitconfig-personal

Paste:

[user]
    name = YOUR_PERSONAL_NAME
    email = YOUR_PERSONAL_EMAIL

Example:

[user]
    name = shubham-01-star
    email = skshubham8348@gmail.com

Save and exit.

Step 3 — Configure Global Git (Work Identity)

Now open the main Git config:

nano ~/.gitconfig

Replace contents with this:

[user]
    name = YOUR_WORK_NAME
    email = YOUR_WORK_EMAIL

[includeIf "gitdir:~/workspace/personal/"]
    path = ~/.gitconfig-personal

[init]
    defaultBranch = main

Example real configuration:

[user]
    name = shubham-kumar-01-dev
    email = shubham.kumar@company.com

[includeIf "gitdir:~/workspace/personal/"]
    path = ~/.gitconfig-personal

[init]
    defaultBranch = main

Explanation:

• Global Git identity = work account

• If repo is inside personal folder, Git loads .gitconfig-personal.

Step 4 — Test the Setup

Personal Folder Test

cd ~/workspace/personal
mkdir git-test-personal
cd git-test-personal
git init

Check identity:

git config user.email

Expected:

your_personal_email

Work Folder Test

cd ~/workspace/work
mkdir git-test-work
cd git-test-work
git init

Check:

git config user.email

Expected:

your_work_email

Step 5 — Test With a Commit

echo "test" > test.txt
git add .
git commit -m "testing git identity"

Check commit author:

git log

Useful Debug Command

If something looks wrong, run:

git config --list --show-origin

This shows which config file is providing each value.

Optional: Terminal Shortcuts for Faster Navigation

While working I noticed I was typing long commands like:

cd ~/workspace/personal

again and again.

So I created two shortcuts:

• personal → jumps to personal workspace

• work → jumps to work workspace

Create the Shortcuts

Open your shell config:

nano ~/.bashrc

Add these lines at the bottom:

alias personal="cd ~/workspace/personal"
alias work="cd ~/workspace/work"

Save the file.

Now reload the terminal configuration:

source ~/.bashrc

How to Use the Shortcuts

Now you can instantly jump to your folders.

Go to personal workspace:

personal

Go to work workspace:

work

Instead of typing long cd commands every time.

This small trick makes the workflow much faster.

Daily Workflow

Personal Projects

personal
git clone https://github.com/username/project.git

Commits will use personal identity.

Work Projects

work
git clone <company-repository>

Commits will use work identity.

Final Workspace Structure

Your projects will eventually look like this:

~/workspace
   ├── personal
   │      ├── portfolio
   │      ├── open-source-tool
   │      └── side-project
   │
   └── work
          ├── backend-api
          ├── auth-service
          └── internal-dashboard

Git automatically chooses the correct identity.

Final Thoughts

Managing multiple Git identities can be frustrating at first.

But once you combine:

• Folder organization

• Conditional Git configs

• Small terminal shortcuts

your workflow becomes clean, safe, and automatic.

You never have to worry about committing with the wrong account again.

And that’s exactly how good developer tooling should work.

#Git #GitHub #DevTips #Developer

open folder

then run cmd on the folder path "

run all these commands one by one

1. npm create vite@latest

2 cd <filename>

step up the project look like this :

3. npm i

4. code . (for open vs code) now close the cmd

now we run all commands in the vs code terminal

1. npm run dev (we see the basic counter app and open that in the browser)

   

   

2. Open File Explorer then go to src--> app.jsx and clear the pre-UI now

4. now we install tailwind CSS

and step all according to our needs like we install tailwind for Vite

read this::- https://tailwindcss.com/docs/guides/vite

we use this website for the background color: https://bg.ibelick.com/

now I start the development

1. src--> components --> Navbar.jsx created ,

src--> components--> Manager.jsx