@tswast, @busunkim96 Can we figure out how to get the bot to give up on this one?

Looks like the tag wasn't created quite right after #753

I manually created https://github.com/googleapis/python-bigquery/releases/tag/v2.21.0

Hopefully that fixes it.

For more context, I primarily created a release PR manually to assure the release notes were sound. Apart from punctuation, which is nice but minor, the main reason was to exclude a CHANGELOG entry that was later reverted, but the bot re-introduced it when re-generating the release notes as PRs got merged.

In other words, it would be good to have more control over the bot through release PR edits, if that's possible.

Word is that it's the release PR branch that is used to determine if to open a PR.

@plamut Were you not able to commit changes to the release branch? Maybe we need to figure out some permissions.

googleapis/release-please#967 has been filed to improve the CHANGELOG edit flow

Merging #760 before we make any releasable commits should fix it.

@tswast The bot was overriding a reverted change in the changelog, it kept adding it back with every new PR. And I wanted to polish a few other things, too, thus forged the original PR branch and submitted it.

I'll report the observed quirks to release-please tomorrow.