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

Enable more linters for Velero #6023

Open
25 of 33 tasks
blackpiglet opened this issue Mar 23, 2023 · 9 comments
Open
25 of 33 tasks

Enable more linters for Velero #6023

blackpiglet opened this issue Mar 23, 2023 · 9 comments
Assignees
Labels

Comments

@blackpiglet
Copy link
Contributor

blackpiglet commented Mar 23, 2023

v1.12

v1.13

  • containedctx: delay due to needing some significant changes to resolve.
  • depguard: dependency guard check is not needed yet.
  • dupword
  • errchkjson
  • gci: the linter requires deleting the blank lines in the import section of some files. It doesn't make sense to me.
  • ginkgolinter
  • gocritic
  • godot: This linter checks whether comments end with a dot. Not that import to me.
  • nilerr
  • noctx
  • nolintlint
  • prealloc
  • predeclared
  • thelper

Describe the problem/challenge you have

Describe the solution you'd like

Anything else you would like to add:

Environment:

  • Velero version (use velero version):
  • Kubernetes version (use kubectl version):
  • Kubernetes installer & version:
  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release):

Vote on this issue!

This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.

  • 👍 for "The project would be better with this feature added"
  • 👎 for "This feature will not enhance the project in a meaningful way"
@blackpiglet blackpiglet self-assigned this Mar 23, 2023
@reasonerjt reasonerjt added this to the v1.12 milestone Apr 18, 2023
@reasonerjt
Copy link
Contributor

@blackpiglet
As discussed we certainly will make enhancements in the linter and static code check, please add more issues to specify what are planned.

@kaovilai
Copy link
Member

Damn..

@blackpiglet
Copy link
Contributor Author

Yeah. There is still a long road ahead.
But don't worry. Some linters require many changes already in progress, such as revive, staticcheck, and stylecheck, of course, also including govet. Thanks for your contribution.

And many linters don't require a lot of hassle. Even no change is needed.

@kaovilai
Copy link
Member

@blackpiglet Try using task list format which makes it easier to navigate back to the epic
ie.

- [x] #739
- [ ] https://github.com/octo-org/octo-repo/issues/740

image

@blackpiglet
Copy link
Contributor Author

@kaovilai Thanks for the suggestion.

@blackpiglet
Copy link
Contributor Author

v1.12 related issues are all resolved.

@reasonerjt
Copy link
Contributor

Will reusing this issue to track the work in v1.13

@reasonerjt reasonerjt added the 1.13-candidate issue/pr that should be considered to target v1.13 minor release label Jul 19, 2023
@reasonerjt reasonerjt removed this from the v1.12 milestone Jul 19, 2023
@reasonerjt reasonerjt removed the 1.13-candidate issue/pr that should be considered to target v1.13 minor release label Aug 23, 2023
@reasonerjt reasonerjt added this to the v1.13 milestone Aug 23, 2023
@blackpiglet
Copy link
Contributor Author

After #7175 merging, v1.13's jobs are done for this task.

@blackpiglet
Copy link
Contributor Author

#7175 is merged. Remove from the v1.13 milestone.

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

No branches or pull requests

3 participants