-
Notifications
You must be signed in to change notification settings - Fork 30
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
Add template validation bot #8
Comments
I want to review our templates as part of this. I also want to consider automation that nudges people to reveal more info vs. hard-closing right off the bat. There was this early AI bot called Dr. Sbaitso that would basically just rubber duck. "How do you feel? Tell me more about your problems." That kind of thing. I find this approach can be an effective way to turn a bad first post into an interesting conversation. "What version are you running? What have you done to debug? What hypotheses do you have?" I'd like to explore automating that vs. automating "No soup for you!" |
Like maybe having a bot watch for the |
Fire on
|
No-op GHA that fires on issue open: https://github.com/chadwhitacre/chadwhitacre-testing-nothing-to-see-here/actions/runs/481292243 Takes 18 seconds to run. Seems like a lot to run on every single issue open. 🐭 |
next step is to pull expected ... clone repo and read |
Choking on https://github.com/getsentry/onpremise/runs/1708876463?check_suite_focus=true
|
Nope. Dutifully performing command substitution. This is another demonstration of the vuln class in getsentry/self-hosted#822, and a confirmation that the first approach to fixing it was indeed insufficient:
|
Done and deployed! 💃 getsentry/self-hosted#845 |
Auto close issues and PRs not adhering to the templates
Example: https://github.com/seferov/pr-lint-action
Todo
onpremise
\r
bug: Add template validation bot #8 (comment)make log download more robust (seeing off-by-ones, probably race condition?)→ Test suite occasionally fails with issue number mismatch #30probably convert to an actiononpremise
sentry-docs
sentry
The text was updated successfully, but these errors were encountered: