redhat-qe-bot
commented
5 months ago Report bugs in Issues
The following are automatically added:
- Add reviewers from OWNER file (in the root of the repository) under reviewers section.
- Set PR size label.
- New issue is created for the PR. (Closed when PR is merged/closed)
- Run pre-commit if
.pre-commit-config.yamlexists in the repo.
Available user actions:
- To mark PR as WIP comment
/wipto the PR, To remove it from the PR comment/wip cancelto the PR. - To block merging of PR comment
/hold, To un-block merging of PR comment/hold cancel. - To mark PR as verified comment
/verifiedto the PR, to un-verify comment/verified cancelto the PR. verified label removed on each new commit push. - To cherry pick a merged PR comment
/cherry-pick <target branch to cherry-pick to>in the PR.- Multiple target branches can be cherry-picked, separated by spaces. (
/cherry-pick branch1 branch2) - Cherry-pick will be started when PR is merged
- Multiple target branches can be cherry-picked, separated by spaces. (
- To build and push container image command
/build-and-push-containerin the PR (tag will be the PR number). - To add a label by comment use
/<label name>, to remove, use/<label name> cancel - To assign reviewers based on OWNERS file use
/assign-reviewers - To check if PR can be merged use
/check-can-merge
oharan2
Currently, if we have more then one matching rule for a failure, the code will take the first rule matched and consider the second a "duplicate" ticket.
The goal is to prioritize it with first check if there's a rule with the same name, otherwise use patterns or duplication.
Workflow example:
exact-*is first in the list of rules andexact-stepis second.exact-stepis identified and paired with both rules.exact-*rule) generates a bug.