--release-bundle fails if --push was called before

I followed the instructions to release a bundle, which worked nicely in general.

However there is an issue if one first calls run.py with the --push option only and then in a second call adds --release-bundle to prepare the email. The push to the repo is rejected because it is not empty anymore. Would it make sense to force the push / rebase or run a git pull before?

To gitlab.hzdr.de:axel.loewe/kcnq1singlecell.git
 ! [rejected]        main -> main (fetch first)
error: failed to push some refs to 'gitlab.hzdr.de:axel.loewe/kcnq1singlecell.git'
hint: Updates were rejected because the remote contains work that you do
hint: not have locally. This is usually caused by another repository pushing
hint: to the same ref. You may want to first integrate the remote changes
hint: (e.g., 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.