Sometimes when git history is diverged, we may experience clt issues when it fails to do something and displays an error message.
To fix it, we should still show the error message but also let the user choose and prompt for confirmation when we will just remove the local branch and actualize it from the remote. In that case, there is only one way to fix it.
We should also double-check if it happens in the case of a new commit, and when we try to push, we should also notify the user about it and suggest refreshing the force-pushed branch from remote to local.
Sometimes when git history is diverged, we may experience clt issues when it fails to do something and displays an error message.
To fix it, we should still show the error message but also let the user choose and prompt for confirmation when we will just remove the local branch and actualize it from the remote. In that case, there is only one way to fix it.
We should also double-check if it happens in the case of a new commit, and when we try to push, we should also notify the user about it and suggest refreshing the force-pushed branch from remote to local.