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

Add Code Coverage Report #131

Merged
merged 4 commits into from
Jan 9, 2025
Merged

Add Code Coverage Report #131

merged 4 commits into from
Jan 9, 2025

Conversation

nomo-app
Copy link
Owner

@nomo-app nomo-app commented Jan 9, 2025

Summary by CodeRabbit

  • CI/CD Improvements

    • Enhanced GitHub Actions workflow for Dart testing
    • Added comprehensive coverage reporting
    • Integrated coverage analysis into documentation deployment process
  • Documentation

    • Updated README with coverage badge
    • Improved document readability and formatting

Copy link

coderabbitai bot commented Jan 9, 2025

Walkthrough

This pull request enhances the GitHub Actions workflow for the Dart project by implementing comprehensive coverage analysis and reporting. A new coverage-report job has been added to process test coverage data, generate HTML reports, and create a coverage badge. The README.md file has been updated to include a coverage badge and improved formatting for better readability without altering the core content.

Changes

File Change Summary
.github/workflows/dart.yml - Added coverage-report job for processing test coverage
- Modified test job to run tests with coverage
- Updated deploy-docs-and-coverage job to include coverage report
README.md - Added coverage badge
- Reformatted text for improved readability
- Minor link formatting adjustment

Sequence Diagram

sequenceDiagram
    participant Workflow as GitHub Actions
    participant Test as Test Job
    participant Coverage as Coverage Report Job
    participant Docs as Deploy Docs Job

    Test->>Test: Run tests with coverage
    Test-->>Coverage: Trigger coverage processing
    Coverage->>Coverage: Generate LCOV report
    Coverage->>Coverage: Create coverage badge
    Coverage-->>Docs: Provide coverage artifacts
    Docs->>Docs: Deploy documentation with coverage
Loading

Possibly related PRs

Suggested reviewers

  • ThomasFercher

Poem

🐰 In the meadow of code, we hop with delight,
Coverage badges shining, oh what a sight!
Tests run with joy, metrics dance in the air,
Our workflow's a garden, tended with care.
Hopping through changes, we celebrate the day,
With each little tweak, we leap and we play! 🌼

Finishing Touches

  • 📝 Generate Docstrings

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.

@nomo-app nomo-app requested a review from ThomasFercher January 9, 2025 13:10
Copy link

@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: 1

🧹 Nitpick comments (6)
.github/workflows/dart.yml (5)

99-106: Add quotes to prevent word splitting in shell commands.

The artifact name construction could be improved to handle special characters safely.

-        run: echo "ARTIFACT_NAME=coverage-$(echo '${{ matrix.test-path }}' | tr '/' '-')" >> $GITHUB_ENV
+        run: echo "ARTIFACT_NAME=coverage-$(echo "${{ matrix.test-path }}" | tr '/' '-')" >> $GITHUB_ENV
🧰 Tools
🪛 actionlint (1.7.4)

100-100: shellcheck reported issue in this script: SC2086:info:1:81: Double quote to prevent globbing and word splitting

(shellcheck)


103-103: the runner of "actions/upload-artifact@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)


122-126: Use null-safe file handling in find command.

The current find command might break with filenames containing spaces or special characters.

-          find coverage-artifacts -name lcov.info -exec echo -a {} \; | xargs lcov -o coverage/lcov.info
+          find coverage-artifacts -name lcov.info -print0 | xargs -0 lcov -o coverage/lcov.info
🧰 Tools
🪛 actionlint (1.7.4)

123-123: shellcheck reported issue in this script: SC2038:warning:2:1: Use 'find .. -print0 | xargs -0 ..' or 'find .. -exec .. +' to allow non-alphanumeric filenames

(shellcheck)


130-136: Add quotes to prevent word splitting in coverage calculation.

The coverage calculation and badge generation could be more robust.

-          COVERAGE=$(lcov --summary coverage/lcov.info | grep "lines......" | cut -d ' ' -f 4 | cut -d '%' -f 1)
+          COVERAGE="$(lcov --summary coverage/lcov.info | grep "lines......" | cut -d ' ' -f 4 | cut -d '%' -f 1)"
-          echo "{\"schemaVersion\": 1, \"label\": \"coverage\", \"message\": \"${COVERAGE}%\", \"color\": \"$(if [ $(echo "$COVERAGE >= 80" | bc -l) -eq 1 ]; then echo 'success'; elif [ $(echo "$COVERAGE >= 60" | bc -l) -eq 1 ]; then echo 'yellow'; else echo 'red'; fi)\"}" > badges/coverage.json
+          echo "{\"schemaVersion\": 1, \"label\": \"coverage\", \"message\": \"${COVERAGE}%\", \"color\": \"$(if [ "$(echo "$COVERAGE >= 80" | bc -l)" -eq 1 ]; then echo 'success'; elif [ "$(echo "$COVERAGE >= 60" | bc -l)" -eq 1 ]; then echo 'yellow'; else echo 'red'; fi)\"}" > badges/coverage.json
🧰 Tools
🪛 actionlint (1.7.4)

131-131: shellcheck reported issue in this script: SC2086:info:2:30: Double quote to prevent globbing and word splitting

(shellcheck)


131-131: shellcheck reported issue in this script: SC2046:warning:4:106: Quote this to prevent word splitting

(shellcheck)


131-131: shellcheck reported issue in this script: SC2046:warning:4:177: Quote this to prevent word splitting

(shellcheck)


156-156: Fix formatting issues.

There are some minor formatting issues in the workflow file:

  • Line 156: Remove trailing whitespace
  • Line 198: Add newline at end of file

Also applies to: 198-198

🧰 Tools
🪛 yamllint (1.35.1)

[error] 156-156: trailing spaces

(trailing-spaces)


103-103: Update GitHub Actions to latest versions.

Several actions are using older versions. Consider updating to the latest versions:

  • actions/upload-artifact@v3@v4
  • actions/checkout@v3@v4
  • actions/download-artifact@v3@v4
  • peaceiris/actions-gh-pages@v3@v4

Also applies to: 112-112, 115-115, 138-138, 153-153, 176-176, 191-191

🧰 Tools
🪛 actionlint (1.7.4)

103-103: the runner of "actions/upload-artifact@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

README.md (1)

35-35: Add hyphens to compound words.

For consistency, add hyphens to the compound term "object-oriented":

-"object oriented architecture"
+"object-oriented architecture"
-"object oriented approach"
+"object-oriented approach"

Also applies to: 102-102

🧰 Tools
🪛 LanguageTool

[misspelling] ~35-~35: This word is normally spelled with a hyphen.
Context: ...ruptions. Also, the WalletKit-C had an "object oriented architecture" that was poorly supported...

(EN_COMPOUNDS_OBJECT_ORIENTED)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 11ab030 and f0e73dd.

📒 Files selected for processing (2)
  • .github/workflows/dart.yml (2 hunks)
  • README.md (5 hunks)
🧰 Additional context used
🪛 actionlint (1.7.4)
.github/workflows/dart.yml

100-100: shellcheck reported issue in this script: SC2086:info:1:81: Double quote to prevent globbing and word splitting

(shellcheck)


103-103: the runner of "actions/upload-artifact@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)


112-112: the runner of "actions/checkout@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)


115-115: the runner of "actions/download-artifact@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)


123-123: shellcheck reported issue in this script: SC2038:warning:2:1: Use 'find .. -print0 | xargs -0 ..' or 'find .. -exec .. +' to allow non-alphanumeric filenames

(shellcheck)


131-131: shellcheck reported issue in this script: SC2086:info:2:30: Double quote to prevent globbing and word splitting

(shellcheck)


131-131: shellcheck reported issue in this script: SC2046:warning:4:106: Quote this to prevent word splitting

(shellcheck)


131-131: shellcheck reported issue in this script: SC2046:warning:4:177: Quote this to prevent word splitting

(shellcheck)


138-138: the runner of "actions/upload-artifact@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)


153-153: the runner of "actions/checkout@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)


176-176: the runner of "actions/download-artifact@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)


191-191: the runner of "peaceiris/actions-gh-pages@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

🪛 yamllint (1.35.1)
.github/workflows/dart.yml

[error] 156-156: trailing spaces

(trailing-spaces)


[error] 198-198: no new line character at the end of file

(new-line-at-end-of-file)

🪛 LanguageTool
README.md

[misspelling] ~35-~35: This word is normally spelled with a hyphen.
Context: ...ruptions. Also, the WalletKit-C had an "object oriented architecture" that was poorly supported...

(EN_COMPOUNDS_OBJECT_ORIENTED)


[uncategorized] ~39-~39: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...er did not support modern null-safe Dart and it was difficult to expand for multiple...

(COMMA_COMPOUND_SENTENCE)


[misspelling] ~102-~102: This word is normally spelled with a hyphen.
Context: ...at sense, we deviate from a traditional object oriented approach. In other words, while we aim...

(EN_COMPOUNDS_OBJECT_ORIENTED)

🔇 Additional comments (2)
.github/workflows/dart.yml (1)

91-96: LGTM! Coverage collection properly integrated.

The test job has been correctly modified to collect coverage data using Dart's built-in coverage tools.

README.md (1)

1-3: LGTM! Coverage badge properly added.

The coverage badge is well-integrated with the existing badges and properly links to the coverage report.

Comment on lines +146 to +154
protoc -I.
--dart_out=grpc:/home/thomas/src/walletkit-dart/lib/src/crypto/tron/rpc
core/Tron.proto core/Discover.proto core/TronInventoryItems.proto
core/contract/common.proto core/contract/account_contract.proto
core/contract/asset_issue_contract.proto core/contract/balance_contract.proto
core/contract/exchange_contract.proto core/contract/market_contract.proto
core/contract/proposal_contract.proto core/contract/shield_contract.proto
core/contract/smart_contract.proto core/contract/storage_contract.proto
core/contract/witness_contract.proto api/api.proto
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Remove or properly document protoc commands.

The protoc commands at the end of the README appear to be development notes and include an absolute path. Consider either:

  1. Removing these commands if they're not meant for users
  2. Moving them to a development documentation file
  3. Converting them into a proper documentation section with context and relative paths

Copy link

@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: 3

🧹 Nitpick comments (1)
.github/workflows/dart.yml (1)

176-189: Add error handling for directory operations.

Consider adding error checking for the directory operations.

       - name: Prepare docs directory
         run: |
+          set -e  # Exit on error
           rm -rf docs
           mkdir -p docs
           cp -R doc/api/* docs/
           mkdir -p docs/coverage docs/badges
           cp -R coverage-report/* docs/coverage/
           cp -R coverage/badges/* docs/badges/
🧰 Tools
🪛 actionlint (1.7.4)

177-177: the runner of "actions/download-artifact@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f0e73dd and c453c59.

📒 Files selected for processing (2)
  • .github/workflows/dart.yml (2 hunks)
  • README.md (5 hunks)
🧰 Additional context used
🪛 actionlint (1.7.4)
.github/workflows/dart.yml

100-100: shellcheck reported issue in this script: SC2086:info:1:81: Double quote to prevent globbing and word splitting

(shellcheck)


103-103: the runner of "actions/upload-artifact@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)


112-112: the runner of "actions/checkout@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)


115-115: the runner of "actions/download-artifact@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)


123-123: shellcheck reported issue in this script: SC2038:warning:2:1: Use 'find .. -print0 | xargs -0 ..' or 'find .. -exec .. +' to allow non-alphanumeric filenames

(shellcheck)


131-131: shellcheck reported issue in this script: SC2086:info:2:30: Double quote to prevent globbing and word splitting

(shellcheck)


131-131: shellcheck reported issue in this script: SC2046:warning:5:106: Quote this to prevent word splitting

(shellcheck)


131-131: shellcheck reported issue in this script: SC2046:warning:5:181: Quote this to prevent word splitting

(shellcheck)


139-139: the runner of "actions/upload-artifact@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)


154-154: the runner of "actions/checkout@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)


177-177: the runner of "actions/download-artifact@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)


192-192: the runner of "peaceiris/actions-gh-pages@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

🪛 yamllint (1.35.1)
.github/workflows/dart.yml

[error] 157-157: trailing spaces

(trailing-spaces)


[error] 199-199: no new line character at the end of file

(new-line-at-end-of-file)

🪛 LanguageTool
README.md

[misspelling] ~35-~35: This word is normally spelled with a hyphen.
Context: ...ruptions. Also, the WalletKit-C had an "object oriented architecture" that was poorly supported...

(EN_COMPOUNDS_OBJECT_ORIENTED)


[uncategorized] ~39-~39: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...er did not support modern null-safe Dart and it was difficult to expand for multiple...

(COMMA_COMPOUND_SENTENCE)


[misspelling] ~102-~102: This word is normally spelled with a hyphen.
Context: ...at sense, we deviate from a traditional object oriented approach. In other words, while we aim...

(EN_COMPOUNDS_OBJECT_ORIENTED)

🔇 Additional comments (6)
.github/workflows/dart.yml (3)

91-96: LGTM! Coverage reporting is properly configured.

The test job has been updated to generate coverage data using the Dart coverage package.


130-137: LGTM! Coverage badge configuration is well implemented.

The coverage badge color logic (red < 60%, yellow 60-80%, green > 80%) provides good visual feedback.

🧰 Tools
🪛 actionlint (1.7.4)

131-131: shellcheck reported issue in this script: SC2086:info:2:30: Double quote to prevent globbing and word splitting

(shellcheck)


131-131: shellcheck reported issue in this script: SC2046:warning:5:106: Quote this to prevent word splitting

(shellcheck)


131-131: shellcheck reported issue in this script: SC2046:warning:5:181: Quote this to prevent word splitting

(shellcheck)


144-151: LGTM! Job dependencies and permissions are correctly configured.

The deploy job properly depends on the coverage-report job and has the necessary permissions.

README.md (3)

1-3: LGTM! Coverage badge is properly implemented.

The coverage badge is well-integrated with the existing badges and links to the coverage report.


Line range hint 6-105: LGTM! Formatting changes improve readability.

The text reformatting enhances readability while preserving the original content.

🧰 Tools
🪛 LanguageTool

[misspelling] ~35-~35: This word is normally spelled with a hyphen.
Context: ...ruptions. Also, the WalletKit-C had an "object oriented architecture" that was poorly supported...

(EN_COMPOUNDS_OBJECT_ORIENTED)


[uncategorized] ~39-~39: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...er did not support modern null-safe Dart and it was difficult to expand for multiple...

(COMMA_COMPOUND_SENTENCE)


146-154: Remove or properly document protoc commands.

The protoc commands appear to be development notes and include an absolute path. Consider either:

  1. Removing these commands if they're not meant for users
  2. Moving them to a development documentation file
  3. Converting them into a proper documentation section with context and relative paths

Comment on lines +197 to +199
commit_message: "docs: update documentation and coverage"
enable_jekyll: false
full_commit_message: "docs: update API documentation"
full_commit_message: "docs: update API documentation and coverage report"
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Add newline at end of file.

Add a newline character at the end of the file to follow POSIX standards.

           full_commit_message: "docs: update API documentation and coverage report"
+
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
commit_message: "docs: update documentation and coverage"
enable_jekyll: false
full_commit_message: "docs: update API documentation"
full_commit_message: "docs: update API documentation and coverage report"
commit_message: "docs: update documentation and coverage"
enable_jekyll: false
full_commit_message: "docs: update API documentation and coverage report"
🧰 Tools
🪛 yamllint (1.35.1)

[error] 199-199: no new line character at the end of file

(new-line-at-end-of-file)

Comment on lines +99 to +106
- name: Set artifact name
run: echo "ARTIFACT_NAME=coverage-$(echo '${{ matrix.test-path }}' | tr '/' '-')" >> $GITHUB_ENV

- name: Upload coverage artifacts
uses: actions/upload-artifact@v3
with:
name: ${{ env.ARTIFACT_NAME }}
path: coverage/lcov.info
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Fix shell script quoting.

The artifact name construction should use quotes to prevent word splitting.

-        run: echo "ARTIFACT_NAME=coverage-$(echo '${{ matrix.test-path }}' | tr '/' '-')" >> $GITHUB_ENV
+        run: echo "ARTIFACT_NAME=coverage-$(echo '${{ matrix.test-path }}' | tr '/' '-')" >> "$GITHUB_ENV"
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- name: Set artifact name
run: echo "ARTIFACT_NAME=coverage-$(echo '${{ matrix.test-path }}' | tr '/' '-')" >> $GITHUB_ENV
- name: Upload coverage artifacts
uses: actions/upload-artifact@v3
with:
name: ${{ env.ARTIFACT_NAME }}
path: coverage/lcov.info
- name: Set artifact name
run: echo "ARTIFACT_NAME=coverage-$(echo '${{ matrix.test-path }}' | tr '/' '-')" >> "$GITHUB_ENV"
- name: Upload coverage artifacts
uses: actions/upload-artifact@v3
with:
name: ${{ env.ARTIFACT_NAME }}
path: coverage/lcov.info
🧰 Tools
🪛 actionlint (1.7.4)

100-100: shellcheck reported issue in this script: SC2086:info:1:81: Double quote to prevent globbing and word splitting

(shellcheck)


103-103: the runner of "actions/upload-artifact@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

Comment on lines +122 to +126
- name: Merge coverage reports
run: |
mkdir -p coverage
find coverage-artifacts -name lcov.info -exec echo -a {} \; | xargs lcov -o coverage/lcov.info

Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Use null-terminated file handling for safety.

The current find/xargs command may break with filenames containing spaces or special characters.

-          find coverage-artifacts -name lcov.info -exec echo -a {} \; | xargs lcov -o coverage/lcov.info
+          find coverage-artifacts -name lcov.info -print0 | xargs -0 lcov -o coverage/lcov.info
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- name: Merge coverage reports
run: |
mkdir -p coverage
find coverage-artifacts -name lcov.info -exec echo -a {} \; | xargs lcov -o coverage/lcov.info
- name: Merge coverage reports
run: |
mkdir -p coverage
find coverage-artifacts -name lcov.info -print0 | xargs -0 lcov -o coverage/lcov.info
🧰 Tools
🪛 actionlint (1.7.4)

123-123: shellcheck reported issue in this script: SC2038:warning:2:1: Use 'find .. -print0 | xargs -0 ..' or 'find .. -exec .. +' to allow non-alphanumeric filenames

(shellcheck)

@nomo-app nomo-app merged commit 07fce56 into main Jan 9, 2025
12 checks passed
@nomo-app nomo-app deleted the add_code_coverage branch January 9, 2025 13:23
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