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: add linter to integration build tag #1102

Merged
merged 1 commit into from
Nov 9, 2023

Conversation

pmalek
Copy link
Member

@pmalek pmalek commented Nov 9, 2023

No description provided.

@pmalek pmalek self-assigned this Nov 9, 2023
@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (b0bc8b9) 32.89% compared to head (de25206) 32.89%.
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1102   +/-   ##
=======================================
  Coverage   32.89%   32.89%           
=======================================
  Files         103      103           
  Lines       12839    12839           
=======================================
  Hits         4223     4223           
  Misses       8207     8207           
  Partials      409      409           

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

@pmalek pmalek marked this pull request as ready for review November 9, 2023 12:44
@pmalek pmalek requested a review from a team November 9, 2023 12:44
Copy link
Collaborator

@GGabriele GGabriele left a comment

Choose a reason for hiding this comment

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

Thanks!

@pmalek pmalek merged commit a1015b6 into main Nov 9, 2023
34 checks passed
@pmalek pmalek deleted the add-linter-to-integration-build-tag branch November 9, 2023 13:39
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.

3 participants