# data[].attributes.headline
What kind of Branching strategy works for you?

# data[].attributes.subject
What kind of Branching strategy works for you?

# data[].attributes.body
I have always been partial to feature branching, but would be interested to know if there is anything that works better for others.

# data[].attributes.body
How best to handle a long lived branch. When the main branch is rapidly evolving.

# data[].attributes.body
Basically how do you organize your libraries. Mono-repo or polyrepos. I've done both

# data[].attributes.headline
What's your most underrated git command?

# data[].attributes.subject
What's your most underrated git command?

# data[].attributes.body
Delete a bunch of branches without needing to re-clone repo? (CLI)

# data[].attributes.headline
How to filter git commit history that has been committed by a particular user?

# data[].attributes.subject
How to filter git commit history that has been committed by a particular user?

# data[].attributes.body
I've been tinkering a little bit with Skim. It's been an interesting experience of piping in input to an interactive cli fuzzy finder and I wanted to share a couple of commands that I've been using

# data[].attributes.body
How do I find the commit that introduced a new bug?

# data[].attributes.body
I get it.. but I don't get it.

Something about forgetting to pull from main before creating a branch? 🫣

# data[].attributes.body
We've all done it at least once in our lives -- we've committed changes that we shouldn't have. What's the best way to undo them, whether it's just local, pushed to remote, or pushed & merged with main?

# data[].attributes.body
This is a new tool that I'm trying out to manage multiple clones of a repo so that I can have parallel work done without switching branches all the time.

# data[].attributes.attachment_link.description
git-worktree - Manage multiple working trees

# data[].attributes.body
I can do a short show-and-tell of how I structure my Git commits to tell the story of my project.