Closed cccsss01 closed 3 weeks ago
Hi @cccsss01. Thanks for your PR.
PRs from untrusted users cannot be marked as trusted with /ok-to-test
in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all
.
I understand the commands that are listed here.
/release-note-none
/lgtm /approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: mhenriks
The full list of commands accepted by this bot can be found here.
The pull request process is described here
@cccsss01: The following test failed, say /retest
to rerun all failed tests or /retest-required
to rerun all mandatory failed tests:
Test name | Commit | Details | Required | Rerun command |
---|---|---|---|---|
pull-cdi-goveralls | 432df9878f7256988caa48a11d479de789d303f5 | link | false | /test pull-cdi-goveralls |
I'm thinking this is a problem with the unit tests?
/retest-required
The override Defaults didn't work for me, I updated them to what did work for me however i'm not sure how to check them, as the status of the CDIS object still shows the old settings. Adding information that states how to update it would be beneficial.
I also added docs that modifies the CDI directly.