/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.
You are here

 andrew.yurisich.com
Squashed Branches for Pull Requests · Andrew Yurisich
| | www.simpleprimate.com
Git rebase to the rescue
1.2 parsecs away

Travel
| | The other day I found myself having serious trouble publishing a new post to my blog. I was able to solve the problem through the use of Git rebase and I thought I would share my experience in case somebody else happens to go through the same thing.
| | blog.kdgregory.com
blog.kdgregory.com: Stupid Git Tricks: Interactive Rebase
1.2 parsecs away

Travel
| | I like to provide a nice, clean history in my pull requests. Reviewers should be able to follow each commit, and see how the functional...
| | andreabergia.com
git rebase --interactive · Andrea Bergia's Website
1.2 parsecs away

Travel
| | Git has an excellent tool designed to help you reorder the commit history: interactive rebase. This can be excellent if you want to keep the history clean, so that it helps other programmers understand the logic behind the changes rather than the actual sequence of commits. Let's walk through an example. Let's write some history Link to heading Let's start by creating an empty project in a new directory:
| | davidalfonso.es
Updating my Neovim config from upstream - david alfonso
9.7 parsecs away

Travel
| [AI summary] The article explains how to update a Neovim configuration repository by merging changes from the upstream LunarVim/Launch.nvim repository and synchronizing it with a dotfiles repo that uses it as a submodule.