Skip to content

git fixup

Make rewriting history great again

explain

Intro

  1. What it is not? Not another basics tutorial.
  2. Why? Usually not time to explain.
  3. What it is it? How to make your git history great again.

linear

source: https://pypi.org/project/git-mr-linear/

clean&clear

source: https://www.clean-flo.com/product/cc-clean-clear-concentrated-enzymes-1-gal/

What git documentation says about rebase:

quote from https://git-scm.com/book/en/v2/Git-Branching-Rebasing

One point of view on this is that your repository’s commit history is a record of what actually happened.

quote from https://git-scm.com/book/en/v2/Git-Branching-Rebasing

The opposing point of view is that the commit history is the story of how your project was made. You wouldn’t publish the first draft of a book, so why show your messy work? When you’re working on a project, you may need a record of all your missteps and dead-end paths, but when it’s time to show your work to the world, you may want to tell a more coherent story of how to get from A to B.

Project layout

main.py         # Simple http server in python.
README.md       # Simple Readme file.