Danger Bot 2.0 Use Case
The below table demonstrates an elaborated use case of the Danger Bot 2.0.
| Steps | Comments | Explanation |
|---|---|---|
| 1 |  |
An initial pull-request comment created by the Danger Bot 2.0. |
| 2 |  |
When students add a new comment /dispute 846d e29c 4805, the bot will immediately reply to students and notify the teaching staff to review student code and especially check for guideline violations associated with those UUIDs. |
| 3 |  |
After inspecting student-submitted code, the teaching staff cancel one or more unresolved violations by inserting a new comment on the pull-request page /cancel 61df 846d 4f9c 9e09. The new comment will eventually trigger the bot to adjust its feedback. |
| 4 |  |
The canceled violations are moved to the bottom of the table, with strikethrough messages and green check icons in front of the message. Note that teaching staff can cancel zero or more guideline violations disputed by students, along with other unresolved violations that they think can be bypassed. |
| 5 |  |
After students submit new code changes, the bot check the code again and mark some guideline violations (7d1a and e29c) as resolved. |
| 6 |  |
The teaching staff always have the right to bypass the decision of the bot by adding a new comment with message /confirm e29c. |
| 7 |  |
The violation e29c that cancelled by the bot becomes unresolved again. |
References
/end
