4 ms·
Please, never rebase published commits if you are an open source project. If your project is used as a submodule anywhere, it screws up release tags hard.
by lostmsu 8y ago
Please, never rebase published commits if you are an open source project. If your project is used as a submodule anywhere, it screws up release tags hard.
- Joky 8y agoThis is about rebasing "user branches" and/or "pull-requests", if your project is referencing un-merged pull-request as a submodule, there is something fishy.
- lostmsu 8y ago> if your project is referencing un-merged pull-request as a submodule, there is something fishy I did not mean incomplete pull requests, I meant master and release branches. Though using unmerged stuff is quite common if the project is yet without an established release process, or not maintained well.
- cryptonector 8y agoYou're right, but no one is proposing to rebase the upstream. So many users think that rebase == lie about history... That's just not what any of us rebase proponents ever do -- we do not rebase upstreams. Indeed, the upstreams I manage disallow non-fast-forward pushes, yet I rebase all the time, just not the upstreams.