No force-pushing when there are no updates

[jonathanloske]

It would be nice if a commit/branch could stay untouched if there are no changes to it.

Current behavior
Whenever git review is run, there is a force-push for all commits/branches, no matter if there were any changes or not. This creates unnecessary overhead as it triggers pipelines and creates visual clutter.

For example, if git review is run twice in a row, all affected commits/branches will be force-pushed twice.

Desired behavior
git review only touches branches if there are any changes in them, ie fixups.

[tjamet]

Hi!

Thanks for raising.
In principle, maiao will do 2 things:

1. rebase your changes on top of the target branch. you can disable this by using the --no-rebase
2. remove any merged commit and fixup (i.e. PR)

if your branch is already based on the target branch, it won't do the rebase.

Could it be that during the life time of the PR, the target branch (i.e. master or main in general) has been updated?
In this case, would the --no-rebase help in this situation?

[jonathanloske]

There were no updates in between. As mentioned, this behavior is visible when running git review twice in a row.

[tjamet]

Would you have the ability to run it twice in a verbose mode (anonymising private fields)?

indeed, this workflow, in standard conditions, is the one I use and I don't get any commit update as you can see in the PR, no force push is visible there.