Skip to content
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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

hutchic
Copy link

@hutchic hutchic commented Apr 15, 2024

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

@jenkins-x-bot
Copy link
Contributor

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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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.

@hutchic hutchic changed the title chore: this warning isn't actionableso let's remove it chore: this warning isn't actionable so let's remove it Apr 15, 2024
@jrx-sjg
Copy link

jrx-sjg commented May 8, 2024

Someone can check this? The warning is VERY annoying.

@msvticket
Copy link
Member

/ok-to-test

@msvticket
Copy link
Member

/approve

@jenkins-x-bot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jrx-sjg
Copy link

jrx-sjg commented May 9, 2024

@hutchic Can you take a look on this?

@hutchic
Copy link
Author

hutchic commented May 9, 2024

@jrx-sjg not really no -- sorry. My time got occupied elsewhere

@jenkins-x-bot
Copy link
Contributor

@hutchic: The following test failed, say /retest to rerun them all:

Test name Commit Details Rerun command
pr ca12c21 link /test

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.

@jrx-sjg
Copy link

jrx-sjg commented May 16, 2024

Hi @hutchic , the PR build failed because an used import has been left on pkg/plugins/trigger/pull-request.go.

CGO_ENABLED=0 GOOS=linux GOARCH=amd64 GO111MODULE=on go build -ldflags "-X github.com/jenkins-x/lighthouse/pkg/version.Version='-dev+b331b30'" -o bin/webhooks cmd/webhooks/main.go
# github.com/jenkins-x/lighthouse/pkg/plugins/trigger
pkg/plugins/trigger/pull-request.go:31:2: "github.com/pkg/errors" imported and not used
make: *** [Makefile:76: build-webhooks-linux] Error 1
Error: Process completed with exit code 2.

Can you please delete it and commit the changes so the PR can go on?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants