Summary

Updater creates PRs without triggering the repository's normal pull_request CI when changelog-entry: false.

What happened

This happened in getsentry/sentry-dotnet#5189, where changelog-entry: false is set. The PR branch was created, but the final create-pull-request pass had nothing to push:

Branch 'deps/modules/sentry-native' is even with its remote and will not be updated

No PR CI ran for the created commit.

For reference, the same update in getsentry/sentry-godot#679 did run CI because changelog-entry defaulted to true. The updater edited CHANGELOG.md after creating the PR, force-pushed the branch, and that produced a pull_request synchronize event.

Expected

Newly created updater PRs should trigger existing pull_request CI regardless of whether a changelog entry is written.