Allow the option to leverage --force in git push about git HOT 4 CLOSED

forcing the push would allow us to override specific requirements that may exist (such as GitHub status checks)

i'm not aware of this being related. forcing a git push is typically related to pushing when the local HEAD does not match the remote HEAD (thus clobbering the remote commits that are different from the ones being pushed). can you point to documentation about how a force push would relate to overriding requirements like status checks?

from git.

I agree, I am unable to reproduce the behavior I previously saw multiple times, probably was a mistake on my side where I was not actually enforcing something and --force made me think it was the key differentiator. Thanks

from git.

Hello, I think this will be a good feature. For example, in a monorepo when you make a release, and in that release, you have two affected apps, you want to generate two different changelogs. In my case, I generate two child pipelines and make the release independently, so the problem is that the first pipeline push, for example, apps/app1/changelog.md ok, and the second pipeline fails because the master branch was updated ... is annoying cuz I only want to update the changelog.md. Exists any possibility of adding this feature or re-open this issue?

from git.

@lukas-henry The issue is that the remote will only have one of those changelogs. Your best bet is trying to pull the changes from the git remote just before making them on the release

from git.