-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scope commands #211
Comments
Sounds reasonable. I was already thinking of applying something similar as dependabot. |
Using @otterdog is not a good idea, as it will tag the user otterdog, which exists: |
Some other prefixes that might work:
my preference would be |
Good catch about |
👍 |
Currently, the commands for Otterdog, such as verify, merge, etc., are not scoped. They can be placed anywhere within the comment body as long as they start with a
/
. This approach could potentially lead to confusion, unintended consequences, or even conflicts with other applications.This ticket aims to discuss the adoption of scoped commands, similar to how Dependabot operates (https://docs.github.com/en/code-security/dependabot/working-with-dependabot/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands), for example:
Thoughts?
The text was updated successfully, but these errors were encountered: