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

Reproduce linting checks from the main repo #121

Merged
merged 16 commits into from
Jan 31, 2025

Conversation

danish9039
Copy link
Contributor

Which problem is this PR solving?

Description of the changes

  • Reproduce linting checks from the main repo to jaeger-idl repo

How was this change tested?

Checklist

.github/workflows/ci-lint-test.yml Show resolved Hide resolved
.github/workflows/ci-lint-test.yml Outdated Show resolved Hide resolved
.github/workflows/ci-lint-test.yml Outdated Show resolved Hide resolved
.github/workflows/ci-lint-test.yml Outdated Show resolved Hide resolved
.github/workflows/ci-lint-test.yml Outdated Show resolved Hide resolved
Makefile Outdated Show resolved Hide resolved
internal/tools/empty.go Outdated Show resolved Hide resolved
.gitignore Outdated Show resolved Hide resolved
.gitignore Outdated Show resolved Hide resolved
Makefile Outdated Show resolved Hide resolved
Makefile Outdated Show resolved Hide resolved
Makefile Outdated Show resolved Hide resolved
Makefile Outdated Show resolved Hide resolved
Makefile Outdated Show resolved Hide resolved
Makefile Outdated Show resolved Hide resolved
Signed-off-by: danish9039 <[email protected]>
@danish9039
Copy link
Contributor Author

danish9039 commented Jan 23, 2025

Screenshot from 2025-01-23 17-43-08
after running make lint-go i encountered these error , most probably caused by last pr in idl repo where files were added into model/v1
@yurishkuro do i need to fix these lint-go errors , otherwise lint checks wont pass success fully ?

@yurishkuro
Copy link
Member

why are we not getting these errors in jaeger repo?

@danish9039
Copy link
Contributor Author

why are we not getting these errors in jaeger repo?

because main jaeger repo uses .golangci.yaml in which errorcheck is disabled
image

@yurishkuro
Copy link
Member

the objective was to use the same settings as the main repo

danish9039 and others added 3 commits January 24, 2025 17:08
Signed-off-by: danish9039 <[email protected]>
.
Signed-off-by: danish9039 <[email protected]>
go.mod Outdated Show resolved Hide resolved
Copy link

codecov bot commented Jan 28, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.85%. Comparing base (68c7c18) to head (3028884).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #121   +/-   ##
=======================================
  Coverage   87.85%   87.85%           
=======================================
  Files          12       12           
  Lines         568      568           
=======================================
  Hits          499      499           
  Misses         67       67           
  Partials        2        2           

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

Signed-off-by: danish9039 <[email protected]>
Signed-off-by: danish9039 <[email protected]>
.golangci.yaml Outdated Show resolved Hide resolved
.golangci.yaml Outdated Show resolved Hide resolved
Makefile Show resolved Hide resolved
Makefile Outdated Show resolved Hide resolved
danish9039 and others added 3 commits January 31, 2025 16:33
Signed-off-by: danish9039 <[email protected]>
Signed-off-by: danish9039 <[email protected]>
Makefile Show resolved Hide resolved
@yurishkuro yurishkuro merged commit 85dae6f into jaegertracing:main Jan 31, 2025
5 checks passed
@yurishkuro
Copy link
Member

Thanks!

yurishkuro pushed a commit that referenced this pull request Jan 31, 2025
## Which problem is this PR solving?
- part of jaegertracing/jaeger#6570

## Description of the changes
- extracted`
https://raw.githubusercontent.com/jaegertracing/jaeger/main/scripts`
into a variable `$(SCRIPTS_URL)`
#121 (comment)

## How was this change tested?
- 

## Checklist
- [X] I have read
https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
- [x] I have signed all commits
- [x] I have added unit tests for the new functionality
- [x] I have run lint and test steps successfully
  - for `jaeger`: `make lint test`
  - for `jaeger-ui`: `npm run lint` and `npm run test`

Signed-off-by: danish9039 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants