Is there a way to dynamically change config from merged PR to PR?

**Is your feature request related to a problem? Please describe.**

One way or another, we'd like to skip/alter the release PR during some scenarios but normally default to configured behaviour.

**Describe the solution you'd like**
- A way to detect that a given feature PR is meant to skip creating a release PR or alter in such a way that release-please or another system can auto-merge the release PR. Could be label, something in the body of the feature PR, etc.
- As stated above, either a PR is skipped altogether (while still making the commit and creating the release/tag,) the PR is merged by release-please if all status checks are green, or even something like adding a special label if it's better for another tool to pick up that work.

**Describe alternatives you've considered**
I suppose the change log or body of the release PR could be scraped and verify that the feature PR has a signal to automerge, but was hoping something like additional labels would be seen as a useful feature in release-please.

We use github actions so if there's a known in-between step to achieve this I'd be happy to try that instead.

**Additional context**
Though my team has been happily using release please for 3 or 4 years, as we try to evangelize it to developers they say that some of their commits could build up in a release but some are just ready to be shipped and bump the version and having to manually review a PR would slow down their velocity...

That being said, I was curious if maybe there was interest in dynamic configurations from PR to PR.