Show warnings in comment (for now: regression PR not against master) #57
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A first attempt to show helpful warnings (or errors) to a PR submitter (#8).
In the first commit this adds
warnings.d
where in the future more warning generator can lay. This commit doesn't modify the output.The second commit extends the bugzilla query by requesting more attributes (e.g. severity)
The third commit combines the first two and emits a warnings when a critical/major/regression/blocking PR isn't based onto stable
Again this is meant as first iteration and we probably have to fine tune this (and can hopefully add more warning generators).
One refactoring step that we should do in any case is to find a common "Cache" format for all information already requested by the diverse APIs - passing them around as function parameters doesn't scale that well.