Force push even if repository is up to date with origin

[palukku]

Version

0.16.1

Operating System

Windows

Distribution Method

msi (Windows)

Describe the issue

When having two remotes I select a branch from one of them on the left (1.) then I apply this branch to the workspace and see (2.) that I can start working on it but it immediately says "force push" (3.) even if the origin branch is the exact same and nothing changed (but it says some unpushed)

How to reproduce (Optional)

No response

Expected behavior (Optional)

It should say that it is up to date and new changes should be appended to the top and than be aple to normally push to it instead of force pushing, force pushing only if changes in old commits are made.

Relevant log output (Optional)

[Byron]

Thanks a lot for reporting!

This will be fixed with the upcoming rewrite of the underlying functionality. The current implementation will always rebase your branch even if that wouldn't be needed technically, which makes certain workflows impossible.

[mkotsbak]

This is important as force pushing creates unnecessary conflicts for collaborators.