Image credit: Illustration created with Midjourney, prompt by the author.
Image prompt
“An illustration representing cloud computing”
Git Survival Guide
This series is a practical guide to Git and GitHub workflows, with a focus on the issues that actually slow people down: diverged histories, recovery, safe collaboration, and confident troubleshooting.
Part 2: Pushing Your New Project to GitHub (Clean First Push Workflow)
Coming Soon
A reliable first-push workflow for new projects: initialize Git, create a clean commit, connect to GitHub, push securely, and avoid common authentication mistakes.
This post is currently being written and will be published soon.
Part 13: GitHub Webhooks: Triggering Python Automation Safely
Coming Soon
A practical setup for GitHub webhooks that trigger Python automation, with signature verification, event filtering, and safe execution patterns.
This post is currently being written and will be published soon.
Part 14: Git Tango: Dancing with Divergent Branches
Coming Soon
This Git tutorial delves into the process of reconciling divergent branches, providing step-by-step guidance for developers. By understanding the current branch status and updating the local repository, users gain a solid foundation for branch reconciliation. The tutorial covers merging branches to combine changes and resolving conflicts that may arise during the merge process. Additionally, it explores the concept of rebasing branches to maintain a linear commit history. With these techniques, developers can effectively manage divergent branches in their Git workflow, promoting collaboration and efficient code integration.
This post is currently being written and will be published soon.
Part 15: Git Failed to Push Some Refs
Coming Soon
I was away from my big MAC computer and did some repository updates using my laptop. When arriving back, I could not push an update from my big MAC computer. Git updates were rejected because my current branch is behind. That happens quite often when we should integrate the remote changes before pushing git updates. Herein I am sharing possible solutions in detail.
This post is currently being written and will be published soon.
Part 16: Git Push from Branch to Master
Coming Soon
What do you call a developer who's afraid of the dark? A Git-in-the-middle attacker! But seriously, if you've ever seen a warning message about a changed SSH host key while pushing code changes, don't panic - it might just be a legitimate update. To fix the issue, simply delete the saved RSA key fingerprint and let the SSH client verify the new one. And remember, always keep an eye out for those pesky man-in-the-middle attackers lurking in the shadows! You can learn how to create and use SSH keys, explained so simply in this post.
This post is currently being written and will be published soon.
Part 33: Your GitHub Token Is Hiding in Plain Sight: Keep Secrets Out of .git/config
Coming Soon
Your GitHub token can sit in plain text inside .git/config. The file is never pushed, so it feels safe — but the token is still exposed on your machine. Here is how to store credentials properly, switch to SSH, and rotate a leaked token.
This post is currently being written and will be published soon.
Each post builds on the previous one, so reading them in order is recommended. Each post also works on its own if you need to jump to a specific topic.