Actions
action #118582
closedcoordination #96596: [qe-core][CI] CI/CD and Coding style improvements
[qe-core][CI][timeboxed:24h] Provide automated feedback on PR's when one or more checks fail
Status:
Rejected
Priority:
Normal
Assignee:
Category:
Spike/Research
Target version:
Start date:
2022-10-13
Due date:
% Done:
0%
Estimated time:
Difficulty:
Sprint:
QE-Core: October Sprint (Sep 28 - Oct 26)
Description
We've all seen the problems when something fails in the CI, and have to spend some time trying to figure out what's broken, by using something like stiky-pull-request-comment we should be able to get some effective feedback, that helps the person who created the PR to understand what went wrong.
In an ideal world, we could be using something that provides a more verbose output like GitHub shows for RuboCop which could be applied for Tidy, or some of the other checks we have for things like yaml schedules, or coding rules.
https://github.com/marocchino/sticky-pull-request-comment
Suggestions¶
- Try out an alternative for comments either by directly writing code or by using marocchino/stiky-pull-request-comment as means to provide feedback on failing tests
- We don't necessarily need to use Perl for this solution.
Acceptance Criteria¶
- Possible alternatives are documented on this ticket
- Comments provide the name of the offending file, and line
Actions