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

Revert "Add loopclosure linter" #7083

Merged
merged 1 commit into from
Jul 10, 2023

Conversation

pierDipi
Copy link
Member

@pierDipi pierDipi commented Jul 7, 2023

Reverts #7079

It causes

  Running [/home/runner/golangci-lint-1.52.0-linux-amd64/golangci-lint run --out-format=github-actions --new-from-patch=/tmp/tmp-1767-brlK8gkkRq5N/pull.patch --new=false --new-from-rev= --go=1.20] in [] ...
  level=error msg="Running error: unknown linters: 'loopclosure', run 'golangci-lint help linters' to see the list of supported linters"

Maybe the version we use in CI doesn't support this linter

@knative-prow knative-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 7, 2023
@knative-prow knative-prow bot requested a review from creydr July 7, 2023 09:06
@knative-prow knative-prow bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jul 7, 2023
@knative-prow knative-prow bot requested a review from odacremolbap July 7, 2023 09:06
@codecov
Copy link

codecov bot commented Jul 7, 2023

Codecov Report

Patch and project coverage have no change.

Comparison is base (1e96c78) 78.31% compared to head (a96b3ee) 78.31%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #7083   +/-   ##
=======================================
  Coverage   78.31%   78.31%           
=======================================
  Files         250      250           
  Lines       13291    13291           
=======================================
  Hits        10409    10409           
  Misses       2351     2351           
  Partials      531      531           

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

Copy link
Member

@creydr creydr left a comment

Choose a reason for hiding this comment

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

/lgtm

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label Jul 7, 2023
@knative-prow
Copy link

knative-prow bot commented Jul 7, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: creydr, pierDipi

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

@creydr
Copy link
Member

creydr commented Jul 10, 2023

/retest

@knative-prow knative-prow bot merged commit ed05a35 into main Jul 10, 2023
21 of 25 checks passed
g1rjeevan pushed a commit to g1rjeevan/eventing that referenced this pull request Jul 20, 2023
Reverts knative#7079

It causes

```
  Running [/home/runner/golangci-lint-1.52.0-linux-amd64/golangci-lint run --out-format=github-actions --new-from-patch=/tmp/tmp-1767-brlK8gkkRq5N/pull.patch --new=false --new-from-rev= --go=1.20] in [] ...
  level=error msg="Running error: unknown linters: 'loopclosure', run 'golangci-lint help linters' to see the list of supported linters"
  ```

Maybe the version we use in CI doesn't support this linter
@pierDipi pierDipi deleted the revert-7079-add-loopclosure-linter branch July 26, 2023 10:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants