3 ms·
> That's why you never rebase a published branch. My problem with that is my coworkers and I usually work on our own feature branch. Ideally I wouldn't push mi
by valtron 13y ago
> That's why you never rebase a published branch.
My problem with that is my coworkers and I usually work on our own feature branch. Ideally I wouldn't push mine to the central repository until I'm done, so I can rebase on master without changing the public history, but at the end of the day I don't like to leave code only on my computer (what if my hard drive blows up??) so I push everything I don't want to lose.
- jsaxton86 13y agoGit is designed so that branching is cheap. Why not create your own development branch off of the feature branch? Then use the feature branch as an integration-only branch?
- nfm 13y agoAn alternative would be to push to a private repo, rather than the shared, central repo. Of course, this has it's own pros and cons.