When working on a feature, you might split it into several stacked branches, so you can merge each one separately. But updating such branches can be annoying since you have to manage them independently. Git 2.38 (2022-10-15) made this management easier with the new --update-refs option, which can rebase a stack of branches at once. Let’s look at a couple of examples.| adamj.eu
The Theatre of Pull Requests and Code Review| meks.quest
You can merge pull requests by retaining all the commits in a feature branch, squashing all commits into a single commit, or by rebasing individual commits from the head branch onto the base branch.| GitHub Docs
At this point, most developers use Git as a tool for collaboration. We have our rote-learned commands to pull, commit, and push. And of course, there's that one coworker who knows a bit more about Git than everyone else, who helps get us back on track whenever our local repos end up in a strange state. But what if I told you that Git can be a valuable tool without ever setting up a remote repository? I'm not just talking about having a working version of your code base to roll back to if you ...| mikkel.ca
In this post I discuss how to use the new Git rebasing feature, --update-refs, and how it makes working with stacked branches/PRs easier.| Andrew Lock | .NET Escapades
A set of rules, their rationale and a short practical guide to creating useful commits.| Bence Ferdinandy
-a --all | git-scm.com
Master documentation versioning with a docs-as-code approach. Explore software versioning, Git methodologies, and the intricacies of REST API versioning.| www.doctave.com
applypatch-msg| git-scm.com
Lets you rewrite Git revision history by rewriting the branches mentioned| git-scm.com
This is a retelling of a presentation I gave at work. In it, I describe a mechanism I've started using to raise the quality of artifacts I check into version control.| packetmischief.ca
