-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
ci(bot): add issue bot #7523
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
ci(bot): add issue bot #7523
Conversation
Codecov Report
@@ Coverage Diff @@
## master #7523 +/- ##
==========================================
- Coverage 93.97% 93.94% -0.04%
==========================================
Files 181 181
Lines 13273 13273
==========================================
- Hits 12473 12469 -4
- Misses 800 804 +4
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome work @mtrezza. I'm not overly familiar with the source code of custom GH Actions so someone with specific expertise might need to look over this.
Thanks for your great work!!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Gret job. LGTM!
🎉 This change has been released in version 5.0.0-beta.1 |
🎉 This change has been released in version 5.0.0 |
New Pull Request Checklist
Issue Description
Adds issue assistance when opening / reopening / editing a new issue.
Closes #7522
Approach
This is a custom bot, not to be published to the GitHub Actions Marketplace, currently with the following basic features:
Here are some test issues to play around with and see the bot in action.
Simply toggle the checkboxes and wait 10 sec to see the bot message changing.
Template
mtrezza/test#19Screenshots
Incorrect template:

Not all checkboxes checked:

All checkboxes checked:

Notes
main
branch of parse-issue-bot repo at the moment, because there will likely be rapid improvements needed during the beta rolloutTODOs before merging