Fixing .env tracking issues with Git

Once I understood the core commands, everything changed, here is the GitHub Crash Course for you ....... . . If you're still stuck on "how to use GitHub properly"? Here's a simple breakdown that helped me (and will help you too): - Repository = Project folder (local or remote) - Commit = Save a snapshot of your changes - Branch - Parallel version of your project - Merge = Combine branches - Clone / Push/Pull = Sync local and remote repos Most Useful Git Commands (with purpose): git init: # Start a new Git repo git clone <url>: # Copy repo to your local system git status: # See current changes git add.: # Stage all files for commit git commit -m "msg": # Save changes with message git push: # Upload changes to GitHub git pull: # Fetch latest from GitHüb git branch: # List branches git checkout -b dev: # Create & switch to new branch git merge dev: # Merge dev into main Connect Swadesh Kumar for more such content Repost it to share in your network Save it if you don't wanna miss it Comment "GitHub" & I'll DM it to you directly. 👇Bonus Tips : ✅ Always write meaningful commit messages ✅ Never push directly to main in a team project ✅ Use .gitignore to avoid uploading junk files

Once I understood the core commands, everything changed, here is the GitHub Crash Course for you ....... If you're still stuck on "how to use GitHub properly"? Here's a simple breakdown that helped me (and will help you too): - Repository = Project folder (local or remote) - Commit = Save a snapshot of your changes - Branch - Parallel version of your project - Merge = Combine branches - Clone / Push/Pull = Sync local and remote repos Most Useful Git Commands (with purpose): git init: # Start a new Git repo git clone <url>: # Copy repo to your local system git status: # See current changes git add.: # Stage all files for commit git commit -m "msg": # Save changes with message git push: # Upload changes to GitHub git pull: # Fetch latest from GitHüb git branch: # List branches git checkout -b dev: # Create & switch to new branch git merge dev: # Merge dev into main Connect Vishakha Singhal ❤️ Repost it to share in your network Save it if you don't wanna miss it Comment "GitHub" & I'll DM it to you directly. 👇Bonus Tips : ✅ Always write meaningful commit messages ✅ Never push directly to main in a team project ✅ Use .gitignore to avoid uploading junk files

Once I understood the core commands, everything changed, here is the GitHub Crash Course for you ....... If you're still stuck on "how to use GitHub properly"? Here's a simple breakdown that helped me (and will help you too): - Repository = Project folder (local or remote) - Commit = Save a snapshot of your changes - Branch - Parallel version of your project - Merge = Combine branches - Clone / Push/Pull = Sync local and remote repos Most Useful Git Commands (with purpose): git init: # Start a new Git repo git clone <url>: # Copy repo to your local system git status: # See current changes git add.: # Stage all files for commit git commit -m "msg": # Save changes with message git push: # Upload changes to GitHub git pull: # Fetch latest from GitHüb git branch: # List branches git checkout -b dev: # Create & switch to new branch git merge dev: # Merge dev into main Connect Vishakha Singhal ❤️ Repost it to share in your network Save it if you don't wanna miss it Comment "GitHub" & I'll DM it to you directly. 👇Bonus Tips : ✅ Always write meaningful commit messages ✅ Never push directly to main in a team project ✅ Use .gitignore to avoid uploading junk files

Once I understood the core commands, everything changed, here is the GitHub Crash Course for you . . If you're still stuck on "how to use GitHub properly"? Here's a simple breakdown that helped me (and will help you too): - Repository = Project folder (local or remote) - Commit = Save a snapshot of your changes - Branch - Parallel version of your project - Merge = Combine branches - Clone / Push/Pull = Sync local and remote repos Most Useful Git Commands (with purpose): git init: # Start a new Git repo git clone <url>: # Copy repo to your local system git status: # See current changes git add.: # Stage all files for commit git commit -m "msg": # Save changes with message git push: # Upload changes to GitHub git pull: # Fetch latest from GitHüb git branch: # List branches git checkout -b dev: # Create & switch to new branch git merge dev: # Merge dev into main Connect Swadesh Kumar for more such content Repost it to share in your network Save it if you don't wanna miss it Comment "GitHub" & I'll DM it to you directly. Bonus Tips: ✅ Always write meaningful commit messages ✅ Never push directly to main in a team project ✅ Use.gitignore to avoid uploading junk files

Once I understood the core commands, everything changed, here is the GitHub Crash Course for you . . If you're still stuck on "how to use GitHub properly"? Here's a simple breakdown that helped me (and will help you too): - Repository = Project folder (local or remote) - Commit = Save a snapshot of your changes - Branch - Parallel version of your project - Merge = Combine branches - Clone / Push/Pull = Sync local and remote repos Most Useful Git Commands (with purpose): git init: # Start a new Git repo git clone <url>: # Copy repo to your local system git status: # See current changes git add.: # Stage all files for commit git commit -m "msg": # Save changes with message git push: # Upload changes to GitHub git pull: # Fetch latest from GitHüb git branch: # List branches git checkout -b dev: # Create & switch to new branch git merge dev: # Merge dev into main Connect VINDHYACHAL . for more such content Repost it to share in your network Save it if you don't wanna miss it Comment "GitHub" & I'll DM it to you directly. Bonus Tips: ✅ Always write meaningful commit messages ✅ Never push directly to main in a team project ✅ Use.gitignore to avoid uploading junk files

I forgot to push to GitLab for three weeks. Switched machines, kept working on GitHub, and only noticed when I tried to clone from the homelab and got a repo that was 47 commits behind. My first fix was a pre-push hook. The hook tried to run git push to GitLab from inside git push to GitHub. That's how I learned that infinite recursion applies to git hooks too. There's a better way that requires zero scripts: git remote set-url --add --push origin https://lnkd.in/gBktpWyn git remote set-url --add --push origin http://gitlab.homelab/user/repo.git That's it. git push now sends to both. One command, nothing to remember. What happens when GitLab is unreachable (like from the corporate laptop): → GitHub ✅ → GitLab ⚠️ fails gracefully — push still succeeds to GitHub GitLab catches up next time I'm home. The 47-commit gap doesn't happen again. The hook that caused infinite recursion? Deleted. If you're writing a shell script to work around a git limitation, check the man page first. The feature is probably already there. #Git #DevOps #RemoteWork #GitHub

From Git Confusion to Clarity: Working with Multiple GitHub Accounts in VS Code Today I tackled something that confuses many beginners (including me 😅): 👉 How to manage multiple GitHub accounts (personal + organization) in VS Code. Here’s what I learned: 🔹 A normal folder ≠ Git repository ➡️ You must run git init to start tracking your project 🔹 Git has 2 levels of identity ✔ Global → default (personal account) ✔ Local (per repo) → can override (organization account) 🔹 Your GitHub identity is based on email, not username ➡️ Always set the correct email for the repo: git config user.name "Your Name" git config user.email "your-org-email@example.com" 🔹 To connect your project to GitHub: git remote add origin https://lnkd.in/gpw74Tm9 🔹 Push your code: git add . git commit -m "initial commit" git push -u origin main 💡 Biggest takeaway: You don’t need to delete or change your personal setup — just configure things per project. This small clarity saves a LOT of confusion while working across teams and organizations. #Git #GitHub #VSCode #Developers #TechJourney

git problem that wasted couple of mins 🧵😅✌️ MR showing a commit I didn’t write. tried reset. tried revert. nothing worked. root cause: my branch forked from a commit that belonged to another branch gitlab diff was showing ancestry, not just my commits fix: git rebase --onto <good-base> <bad-commit> <my-branch> git push --force what this does: replays ONLY your commits on top of the correct base removes unwanted history cleanly lesson: git log = your truth MR diff = ancestry truth they can disagree. when MR shows чужा commits → don’t panic don’t reset → use --onto most underrated git command fr 🔪 #git #gitlab #softwareengineering #developer #builder

The first thing I do when starting a new project is initialize Git and create a repository on Github, Gitlab, or Codeberg. No matter the size of your project, even if it's just a couple of code files for an experiment and you're the only one working on it, I recommend doing it in a version control system. Git allows you to add new lines and remove old lines without worrying about losing anything valuable in your files. You can view the change history and revert to a previous version at any time. If you haven't used it yet, there's a great guide (https://lnkd.in/ez6USXvq) that will introduce you to the basic commands and get you up to speed on workflows. Every project of mine starts with these commands in the console: ``` git init git add . git commit -m 'Init' git remote add origin ... git push -u origin master ``` #VCS #Git #Repository #Github #Gitlab #Codeberg

We’ve all been there: joining a new project, grabbing a fresh cup of coffee, and asking the developer the most basic, innocent question imaginable: "Hey, where's the code repo for your project?" You expect a Github link, maybe a Gitlab URL, or even an ancient SVN server if you're feeling unlucky. What you don't expect is the developer to smile with 100% unshakeable confidence and say: "Oh, I manage versions myself." When I glanced at his screen, the horror truly set in. There was no Git branch, no commit history, just an Outlook inbox bursting with emails sent to himself. Attached to each one was a ZIP file with names that belong in a museum of modern IT nightmares: project_v1.zip project_v2_final.zip https://lnkd.in/emaWfaPd https://lnkd.in/eqM5ae4n I thought it was a joke. I prayed it was a joke. But nope. He cheerfully explained that he just emails himself a copy every time he makes a change. In his mind, it was a perfectly functioning, 100% offline manual distributed version control system. I had to walk away and take a very long sip of my coffee. He had successfully invented email-driven Git... one attachment at a time. Because who needs GitHub when you have Outlook, right? 😅 Read this story and the previous ones on my blog. You can find the link in my bio. #AdventuresInUptime #DevOps #TechHumor #SoftwareEngineering #VersionControl #GitHub