Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • 1
    Forcing a push o feature-branch will impact the rest of the team, and certainly will need some fixing if someone else is in the process of merging their sub-branch back into feature-branch. Commented Jul 18, 2018 at 10:14
  • @Richard is absolutely correct concerning the influence to the rest of the team. But I think that this is exactly the answer to the question. It's pity that it has such bad consequences. Note that you can use --force-with-lease with git push, but it doesn't solve much... Commented Jul 18, 2018 at 11:45
  • 1
    @Richard Yeah, after force push, it does should inform other members. But based on Andrea requirement (update feature-branch and sub-branch while keeping the branch structures), force push is the way which must be passed. Commented Jul 19, 2018 at 7:35