Can the ability to issue Dependabot commands be delegated?

[EliahKagan]

From #1882 (comment):

[..] But I cannot myself close #1878.

Now that this repository is in an organization, permissions are much more fine-grained. If you have suggestions on how to make your life easier, I'd be happy to make adjustments.

For Dependabot PRs specifically, I'm not sure if there's anything that can reasonably be done. Dependabot follows commands issued in comments by users with write access.

(Anyone who can comment can write a comment that looks like it contains a Dependabot command, and this does notify Dependabot. But Dependabot entirely ignores such comments unless the user has write access to the repository. So, for example, I was of course able to post #1878 (comment), but Dependabot did not acknowledge the command.)

Maybe rulesets and CODEOWNERS with branch protection rules can be used with the effect of conferring this ability in a fine-grained way. But I am not sure.

• If write access is given to allow me to issue Dependabot commands, while also being effectively "taken away" by making it so that I cannot push anything that makes changes at any path on any branch, then that might work, so long as Dependabot would itself still be able to carry out commands like @dependabot merge.
• If write access is also given to allow me to also push to the feature branches of Dependabot pull requests (dependabot/** branches), but Dependabot is not restricted in what it can modify, then this is similar to the ability to create and merge an arbitrary pull request to the main branch. Although pushing to Dependabot branches is useful for manually fixing things up, most of the time it is not needed.