TL;DR git rebase --exec "<cmd>" <upstream> (short form -x) appends an exec <cmd> line after every pick in the rebase instruction list, so the command runs in the working tree of each replayed commit. A non-zero exit stops the rebase on that commit with exit code 1. When it stops, fix the …

This is the companion page to my Git and GitHub blueprint - a free three-hour-twenty-minute course that starts at git init and ends with you rewriting history on purpose and resolving merge conflicts without sweating. Everything on this blog - Terraform, Ansible, Kubernetes manifests, this very site - lives in Git, …

GitHub has recently announced their migration to use token-based authentication which means you can no longer use your username and password for GtiHub authentication. You need to create personal access token to continue use of your GitHub Repository. Here is my private GitHub repository which I was trying to clone …

I usually work with multiple projects at once and whenever there is a new feature on which I had to work, I usually create a new Branch from my Master branch and once I am done with the new feature I do create a pull request and after the approval, I do merge my changes from my new Branch to my Master branch. Well, …

TL;DR What it means: git sent its first request (GET <your-url>/info/refs?service=git-upload-pack for clone and fetch, git-receive-pack for push) and the server answered with a redirect to a different path. git only follows a redirect that keeps the same /info/refs?service=... tail; anything else, for example …