-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: this warning isn't actionable so let's remove it #1602
base: main
Are you sure you want to change the base?
Conversation
Hi @hutchic. Thanks for your PR. I'm waiting for a jenkins-x member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. |
Someone can check this? The warning is VERY annoying. |
/ok-to-test |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: msvticket The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@hutchic Can you take a look on this? |
@jrx-sjg not really no -- sorry. My time got occupied elsewhere |
@hutchic: The following test failed, say
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here. |
Hi @hutchic , the PR build failed because an used import has been left on pkg/plugins/trigger/pull-request.go.
Can you please delete it and commit the changes so the PR can go on? |
Based on what I've been able to discern from slack / github jenkins-x/jx#8589 isn't an actionable warning. On top of that it seems backwards compatibility is going to be maintained.
With that in mind let's not create a non-actionable warning