Well that's fine, cause I think merging without rebasing is gross. I want to commit when component x technically works, when I've improved it, when I've rename

Well that's fine, cause I think merging without rebasing is gross. I want to commit when component x technically works, when I've improved it, when I've renamed crap, all the time. I only need those to be 1 commit and after that I can write a nice message that covers what it did. My process for developing the code should be separate from the organization used to store it historically for others to see.