/explore
|
You are here 
|
andrew.yurisich.com | ||
| | | | |
andreabergia.com
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: |
|
| | | | | ||
| | | | |
www.simpleprimate.com
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
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... |
|
| | | | | ||
| | | | |
lisp-journey.gitlab.io
Lem is an awesome project. It's an editor buit in Common Lisp, ready to use out of the box for Common Lisp, that supports more languages and modes (Python, Rust, Elixir, Go, JavaScript, TypeScript, Haskell, Java, Nim, Dart, OCaml, Scala, Swift, shell, asm, but also markdown, ascii, JSON, HTML and CSS, SQL...) thanks to, in part, its built-in LSP support.I took the challenge to add an interactive interface for Git, à la Magit, because you know, despite all its features (good vim mode, project-aware comman... |
|
| | | |||
