Victor, I think force pushing a feature branch is fine if you're the only one working on it. If there are multiple people working on it, and the feature's commits are distributed among a number of repositories, then rebasing on to master would cause some pretty terrible issues for the others devs who would would need to synchronize with the feature branch afterwards.
On Mon, Mar 21, 2016 at 4:48 PM, Victor Dogaru <[email protected]> wrote: > >> On Monday, March 21, 2016 2:51 PM, William Marshall <[email protected] > > > wrote: > > Thanks Will, after reading your e-mail, I found this: > > > > > https://www.atlassian.com/git/tutorials/merging-vs-rebasing/conceptual-overview > > I realized that this page also explains why you need to force-push your > feature branch after you rebased it onto master. We are using this to push > further commits to a remote feature branch which is used on a PR, for > example. > > On Mon, Mar 21, 2016 at 3:15 PM, Dan Debrunner <[email protected]> wrote: > > > > On Monday, March 21, 2016 2:51 PM, William Marshall < > [email protected]> > > wrote: > > > > Thanks Will, after reading your e-mail, I found this: > > > > > > > https://www.atlassian.com/git/tutorials/merging-vs-rebasing/conceptual-overview > > > > > > It has pictures that help explain the concept, which I'm still trying to > > get my head around. > > Dan. > > >
