Replies: 4 comments
-
Yeah, I know we've asked the fabric bot folks about this, but don't think they're working on it. We'd probably need our own bot which figures out how to get the logs from the DevOps pipeline and spits it back out as a PR comment. Probably worth following up with the bot team again though about it. |
Beta Was this translation helpful? Give feedback.
-
I personally don't like bots especially when they add too much noise in the comments section. As you said, it might help but the resolved bot comments should be either hidden or deleted from the comments section. Bots should also detect force-push and react accordingly. When a contributor is new to the Toolkit project, bot should help them out but should stay out of the way as much as possible, like deleting or hiding its own redundant comments, collapsing logs, large ones from its own and from users alike. |
Beta Was this translation helpful? Give feedback.
-
I could see a bot that makes suggestions for trailing whitespace fixes or missing license headers. Not sure how feasible that is, but those are the types of issues I see most commonly. |
Beta Was this translation helpful? Give feedback.
-
How about detecting spelling and grammar mistakes and suggesting fixes. I saw this on some official Microsoft repo a while back but I don't remember which one! |
Beta Was this translation helpful? Give feedback.
-
Describe the problem this feature would solve
When a PR fails in CI when someone did not expect it to (typically because the contributor saw no error locally in VS) someone has to dive into logs to find the issue and either comment on the PR to help the contributor or make a change.
Describe the solution
We add a bot that comments on PR with errors and warnings from the CI pipeline. If possible it should also suggest changes if there is any reasonable default changes (like formatting changes).
Describe alternatives you've considered
Additional context & Screenshots
Beta Was this translation helpful? Give feedback.
All reactions