You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the title of automatic PRs filed as a result of commands from non-privileged users indicate whether the user is requesting a watch or a blacklist, but don't indicate the specific type of request the user is making (e.g., which blacklist the user is requesting to add to). The only way to know is to open the PR and look.
I propose that the titles be reformatted to state something like:
"Silver the Hedgehog: Blacklist website gray\.fur"
This seems important to me since PRs can be approved in chat without opening them up on GitHub. The automatic message posted when a PR is opened only indicates the title, so there is no way to catch, for example, a user mistakenly adding a website to the keyword blacklist without clicking through to GitHub, which users aren't likely to do if the command was executed in a room other than Charcoal HQ.
The text was updated successfully, but these errors were encountered:
gparyani
added a commit
to gparyani/SmokeDetector
that referenced
this issue
Jul 22, 2024
Currently, the title of automatic PRs filed as a result of commands from non-privileged users indicate whether the user is requesting a watch or a blacklist, but don't indicate the specific type of request the user is making (e.g., which blacklist the user is requesting to add to). The only way to know is to open the PR and look.
I propose that the titles be reformatted to state something like:
This seems important to me since PRs can be approved in chat without opening them up on GitHub. The automatic message posted when a PR is opened only indicates the title, so there is no way to catch, for example, a user mistakenly adding a website to the keyword blacklist without clicking through to GitHub, which users aren't likely to do if the command was executed in a room other than Charcoal HQ.
The text was updated successfully, but these errors were encountered: