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

LF-12212 Adapt git action (ensure test coverage) to run only when needed #991

Merged
merged 11 commits into from
Feb 18, 2025

Conversation

mirooon
Copy link
Contributor

@mirooon mirooon commented Feb 11, 2025

Which Jira task belongs to this PR?

LF-12212

Why did I implement it this way?

Checklist before requesting a review

Checklist for reviewer (DO NOT DEPLOY and contracts BEFORE CHECKING THIS!!!)

  • I have checked that any arbitrary calls to external contracts are validated and or restricted
  • I have checked that any privileged calls (i.e. storage modifications) are validated and or restricted
  • I have ensured that any new contracts have had AT A MINIMUM 1 preliminary audit conducted on by <company/auditor>

Copy link
Contributor

coderabbitai bot commented Feb 11, 2025

Walkthrough

The pull request introduces modifications to the GitHub Actions workflow in .github/workflows/enforceTestCoverage.yml by adding a step to check for changes in Solidity files before executing test coverage checks. A new job step named "Check for Solidity file changes" sets an environment variable based on whether any Solidity files have been modified. Subsequent steps are conditioned to run only if Solidity files have changed, and a new step allows skipping tests when no changes are detected. Additionally, a new private variable is added to the CBridgeFacet contract in src/Facets/CBridgeFacet.sol.

Changes

File(s) Change Summary
.github/workflows/enforceTestCoverage.yml Introduced a step to check for changes in Solidity files, conditionally running subsequent steps based on this check, and added a step to skip tests if no Solidity changes are detected.
src/Facets/CBridgeFacet.sol Added a new private immutable variable ICBridge private a; to the CBridgeFacet contract.

Suggested reviewers

  • ezynda3

Warning

Review ran into problems

🔥 Problems

Errors were encountered while retrieving linked issues.

Errors (1)
  • JIRA integration encountered authorization issues. Please disconnect and reconnect the integration in the CodeRabbit UI.

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?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@lifi-action-bot lifi-action-bot marked this pull request as draft February 11, 2025 17:07
@lifi-action-bot
Copy link
Collaborator

Test Coverage Report

Line Coverage: 78.66% (2238 / 2845 lines)
Function Coverage: 84.71% ( 388 / 458 functions)
Branch Coverage: 39.60% ( 221 / 558 branches)
Test coverage (78.66%) is above min threshold (78%). Check passed.

@mirooon mirooon marked this pull request as ready for review February 11, 2025 17:18
Copy link
Contributor

@coderabbitai coderabbitai bot left a 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 (1)
.github/workflows/enforceTestCoverage.yml (1)

10-11: Consider monitoring test file changes.

While filtering for src/** is correct for coverage checks, changes to test files might affect coverage without triggering this workflow. Consider adding a separate workflow or extending this one to notify when test files are modified without corresponding source changes.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 038d342 and 5e52f82.

📒 Files selected for processing (1)
  • .github/workflows/enforceTestCoverage.yml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: run-unit-tests
🔇 Additional comments (1)
.github/workflows/enforceTestCoverage.yml (1)

10-11: LGTM! The path filter optimizes workflow execution.

The addition of the paths filter aligns with the PR objective and improves efficiency by running only when source files are modified.

0xDEnYO
0xDEnYO previously approved these changes Feb 11, 2025
@0xDEnYO 0xDEnYO enabled auto-merge (squash) February 11, 2025 23:51
Copy link
Contributor

@coderabbitai coderabbitai bot left a 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 (3)
.github/workflows/enforceTestCoverage.yml (3)

35-44: Improve the file change detection pattern.

The current grep pattern ^src/.*\.sol|^test/.*\.sol might miss Solidity files in subdirectories. Consider using a more robust pattern or GitHub's built-in path filters.

Apply this diff to improve the pattern:

-          CHANGED_FILES=$(git diff --name-only origin/${{ github.base_ref }}...HEAD | grep -E '^src/.*\.sol|^test/.*\.sol' || true)
+          CHANGED_FILES=$(git diff --name-only origin/${{ github.base_ref }}...HEAD | grep -E '^(src|test)/.*\.sol$' || true)

Alternatively, you could use GitHub's built-in path filters in the workflow trigger:

on:
  pull_request:
    types: [opened, synchronize, reopened, ready_for_review]
    paths:
      - 'src/**.sol'
      - 'test/**.sol'

50-50: Consider optimizing conditional execution.

The repetitive if: env.solidity_changed == 'true' conditions could be simplified by moving them to the job level or using a composite step.

Consider this alternative structure:

jobs:
  enforce-min-test-coverage:
    runs-on: ubuntu-latest
    if: |
      github.event.pull_request.draft == false &&
      contains(github.event.pull_request.changed_files, '.sol')
    steps:
      # ... steps without individual conditions

Or create a composite step to reduce repetition:

jobs:
  enforce-min-test-coverage:
    runs-on: ubuntu-latest
    if: github.event.pull_request.draft == false
    steps:
      - name: Coverage Check
        if: env.solidity_changed == 'true'
        uses: ./.github/actions/coverage-check
        # ... remaining steps moved to composite action

Also applies to: 54-54, 58-58, 62-62, 65-65, 76-76, 155-155


167-169: Enhance skip notification for better visibility.

The current notification could be more informative and visible to PR reviewers.

Consider adding a PR comment when tests are skipped:

       - name: Skip Tests (No Solidity Changes)
         if: env.solidity_changed == 'false'
-        run: echo "No Solidity files changed. Skipping test coverage check."
+        uses: mshick/[email protected]
+        with:
+          repo-token: ${{ secrets.GIT_ACTIONS_BOT_PAT_CLASSIC }}
+          message: |
+            ## Test Coverage Check Skipped
+            
+            No Solidity files were changed in this PR. Test coverage check was skipped.
+            
+            Note: Changes to non-Solidity files do not trigger coverage checks.
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d05f6a6 and b5c3d75.

📒 Files selected for processing (2)
  • .github/workflows/enforceTestCoverage.yml (4 hunks)
  • src/Facets/CBridgeFacet.sol (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • src/Facets/CBridgeFacet.sol
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: run-unit-tests
  • GitHub Check: enforce-min-test-coverage
🔇 Additional comments (2)
.github/workflows/enforceTestCoverage.yml (2)

32-34: LGTM! Setting fetch-depth: 0 is necessary for git history.

The configuration ensures that the complete git history is available for comparing changes with the base branch.


7-9: Verify the required check status in repository settings.

Based on past discussions, this workflow's status as a required check might need adjustment. If it's marked as required in repository settings, PRs with no Solidity changes might be blocked unnecessarily.

Please check:

  1. Repository Settings > Branches > Branch protection rules
  2. Verify if "Enforce Min Test Coverage" is listed under required status checks
  3. Consider the trade-offs:
    • Required: Ensures coverage checks always pass but might block PRs unnecessarily
    • Optional: More flexible but might allow merging without coverage checks

@mirooon
Copy link
Contributor Author

mirooon commented Feb 13, 2025

So to solve it and to keep action reporting and also run min test coverage script only when there is a change for .sol files in src/ and test/ folders. I first check for direct modifications in the action logic. If no new .sol files are detected in these folders the test coverage script is skipped. Let me know your thoughts! @kalote @0xDEnYO

@mirooon mirooon requested a review from 0xDEnYO February 13, 2025 15:24
@0xDEnYO 0xDEnYO merged commit a0c044c into main Feb 18, 2025
29 of 31 checks passed
@0xDEnYO 0xDEnYO deleted the lf-12212-run-ensure-test-coverage-only-when-needed branch February 18, 2025 07:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants