Skip to content

Comments

🌱 chore(lint): Upgrade golanglint from v2.7.2 to v2.8.0 and fix lint issues#1898

Open
camilamacedo86 wants to merge 1 commit intooperator-framework:masterfrom
camilamacedo86:uplint
Open

🌱 chore(lint): Upgrade golanglint from v2.7.2 to v2.8.0 and fix lint issues#1898
camilamacedo86 wants to merge 1 commit intooperator-framework:masterfrom
camilamacedo86:uplint

Conversation

@camilamacedo86
Copy link
Contributor

No description provided.

@openshift-ci openshift-ci bot requested review from anik120 and kevinrizza February 3, 2026 11:04
# even when GOOS/GOARCH are set for cross-compilation of other targets.
GOHOSTOS ?= $(shell $(GO) env GOHOSTOS)
GOHOSTARCH ?= $(shell $(GO) env GOHOSTARCH)
GOHOSTARM ?= $(shell $(GO) env GOHOSTARM)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tmshort bingo get github.com/golangci/golangci-lint/v2/cmd/golangci-lint here is adding those,
I remember that we cannot add those ?
I think you did something to avoid it. Could you please help me out?
Can you please point out me how to fix it?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't recall... :(

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So it seems all is fine.
I think we cannot add those for operator-controller only doing the upstream/downstream dance.
Here shows all fine.

@codecov
Copy link

codecov bot commented Feb 3, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 57.47%. Comparing base (501f99b) to head (25cb920).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1898      +/-   ##
==========================================
- Coverage   57.48%   57.47%   -0.01%     
==========================================
  Files         138      138              
  Lines       13307    13307              
==========================================
- Hits         7649     7648       -1     
- Misses       4476     4477       +1     
  Partials     1182     1182              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 3, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 3, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: perdasilva

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 3, 2026
@perdasilva perdasilva removed the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 3, 2026
@grokspawn
Copy link
Contributor

I have some reservations because this is an update to a new version of bingo as well as a new version of golangci-lint.

Also, when we have lint issues here, we typically:

  1. solve all test suggestions
  2. solve any alpha/* or cmd/alpha/* (this includes the templates)
  3. examine each case which remains, individually, with a bias towards putting in a //nolint comment instead. This code is pretty old and has some indirect failures.

I'll need another pass for 3 above.

Until then, please
/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 3, 2026
@camilamacedo86
Copy link
Contributor Author

Hi @grokspawn

Thank you for looking this one.

Regards: #1898 (comment)

We solved all suggestions.
Do you want to see the issues?
Sorry, I am not sure if I followed what would be required here.

@grokspawn
Copy link
Contributor

Hi @grokspawn

Thank you for looking this one.

Regards: #1898 (comment)

We solved all suggestions. Do you want to see the issues? Sorry, I am not sure if I followed what would be required here.

Can we start by splitting this PR into two?

  1. bingo version update
  2. golangci-lint update and fixes

I have some concerns that the bingo updates might have impacts during vendor repackaging, so I'd prefer to see it handled disjointly.

What I was saying before is that the SQLite-related code is EOL and we generally do not touch it. I haven't made another pass to see if any proposed changes here are in that area, but I'll be happy to review the new PRs!

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

Labels

do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants