-
Notifications
You must be signed in to change notification settings - Fork 338
[2/N] Lint enhancements #1735
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
base: main
Are you sure you want to change the base?
[2/N] Lint enhancements #1735
Conversation
7fe24f7
to
e6fa107
Compare
@wangxiyuan @Yikun This is ready for review |
ci break for upstream change, repairing |
Codecov ReportAttention: Patch coverage is
❌ Your patch check has failed because the patch coverage (79.24%) is below the target coverage (100.00%). You can increase the patch coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## main #1735 +/- ##
==========================================
+ Coverage 71.49% 71.58% +0.09%
==========================================
Files 86 86
Lines 9131 9087 -44
==========================================
- Hits 6528 6505 -23
+ Misses 2603 2582 -21
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Should enable python init check after vllm-project/vllm#20908 merged |
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
044b22d
to
8da6754
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please split PR into 3 job
- https://github.com/jackdewinter/pymarkdown
- Enforce init.py in Python packages
- Lint shell scripts
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
1 similar comment
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
What this PR does / why we need it?
Step of #1241, in the pr,
Does this PR introduce any user-facing change?
How was this patch tested?