-
-
Notifications
You must be signed in to change notification settings - Fork 821
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
Enhance ESLint Disable Check and Code Coverage Disable Check with Detailed Messages #3007
Enhance ESLint Disable Check and Code Coverage Disable Check with Detailed Messages #3007
Conversation
…ditional messages
WalkthroughThe pull request modifies two GitHub workflow Python scripts: Changes
Assessment against linked issues
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
Tip CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
Our Pull Request Approval ProcessThanks for contributing! Testing Your CodeRemember, your PRs won't be reviewed until these criteria are met:
Our policies make our code better. ReviewersDo not assign reviewers. Our Queue Monitors will review your PR and assign them.
Reviewing Your CodeYour reviewer(s) will have the following roles:
CONTRIBUTING.mdRead our CONTRIBUTING.md file. Most importantly:
Other
|
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.
Actionable comments posted: 0
🧹 Nitpick comments (2)
.github/workflows/eslint_disable_check.py (1)
78-78
: Prefer a singular reference when describing the statement.Currently, the print message says “Please remove them” when referring to a singular eslint-disable statement. Consider using “an eslint-disable statement” and “remove it” to clarify the message.
Example suggestion:
- print(f"File {item} contains eslint-disable statement. Please remove them and ensure the code adheres to the specified ESLint rules.") + print(f"File {item} contains an eslint-disable statement. Please remove it and ensure the code adheres to the specified ESLint rules.").github/workflows/code_coverage_disable_check.py (1)
91-91
: Consider adding instructions for remediation.At line 91, the message informs users about the presence of a code coverage disable statement but does not guide them further (unlike line 106). Consider adding a brief directive, such as asking to remove the statement and add tests, to maintain consistent clarity.
Example:
- print(f"File {file_path} contains code coverage disable statement.") + print(f"File {file_path} contains a code coverage disable statement. Please remove it and add appropriate tests.")
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
.github/workflows/code_coverage_disable_check.py
(2 hunks).github/workflows/eslint_disable_check.py
(1 hunks)
🔇 Additional comments (1)
.github/workflows/code_coverage_disable_check.py (1)
106-106
: Ensure consistent messaging style.
Here, you provide actionable information about removing the disable statement and adding tests. That’s excellent. For consistency and clarity across the script, ensure all related messages follow a similar style, so developers receive uniform guidance on next steps.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop-postgres #3007 +/- ##
=====================================================
+ Coverage 29.27% 88.92% +59.65%
=====================================================
Files 300 321 +21
Lines 7546 8408 +862
Branches 1646 1893 +247
=====================================================
+ Hits 2209 7477 +5268
+ Misses 5154 688 -4466
- Partials 183 243 +60 ☔ View full report in Codecov by Sentry. |
81c66d9
into
PalisadoesFoundation:develop-postgres
Issue Number:
Fixes #2594
Summary by CodeRabbit