Skip to content

Update coverage workflow#194

Merged
leynos merged 3 commits intomainfrom
codex/use-shared-action-for-ci-workflow
Jun 20, 2025
Merged

Update coverage workflow#194
leynos merged 3 commits intomainfrom
codex/use-shared-action-for-ci-workflow

Conversation

@leynos
Copy link
Copy Markdown
Owner

@leynos leynos commented Jun 20, 2025

Summary

  • use leynos shared action for uploading coverage
  • document the shared action in coverage docs

Testing

  • cargo clippy -- -D warnings
  • make test
  • markdownlint '**/*.md'
  • nixie docs/*.md

https://chatgpt.com/codex/tasks/task_e_6855e8f441fc8322b0de0f275a714b78

Summary by Sourcery

Adopt a shared GitHub Action for CodeScene coverage uploads and update documentation accordingly

CI:

  • Replace manual CodeScene CLI install and upload steps with the leynos/shared-actions/upload-codescene-coverage action in the CI workflow

Documentation:

  • Update CodeScene CLI documentation to reference the shared action and its checksum verification

Summary by CodeRabbit

  • Chores
    • Updated the workflow to use a shared GitHub Action for uploading CodeScene coverage data, simplifying the CI process.
  • Documentation
    • Revised documentation to reflect the new method for handling CodeScene coverage uploads via the shared GitHub Action.

@sourcery-ai
Copy link
Copy Markdown
Contributor

sourcery-ai Bot commented Jun 20, 2025

Reviewer's Guide

This PR streamlines the CodeScene coverage upload by replacing the hand-rolled install and upload steps in the CI workflow with a standardized shared GitHub Action, and updates the documentation to reflect this change.

Flow diagram for new coverage upload process in CI

flowchart TD
  A[Generate lcov.info] --> B[Use leynos/upload-codescene-coverage Action]
  B --> C[Coverage uploaded to CodeScene]
Loading

File-Level Changes

Change Details Files
Refactor CI workflow to use shared CodeScene coverage upload action
  • Removed manual download, checksum verification, and install script steps
  • Added leynos/shared-actions/upload-codescene-coverage@v1.0.3 with path and format inputs
  • Passed CODESCENE_CLI_SHA256 through environment
  • Cleaned up old cs-coverage upload command
.github/workflows/ci.yml
Update docs to describe the new shared action
  • Replaced manual CLI install description with shared action workflow
  • Explained caching, download, and checksum verification handled by the action
docs/codescene-cli.md

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jun 20, 2025

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The CI workflow for uploading CodeScene coverage data was refactored to use the leynos/shared-actions/upload-codescene-coverage@v1.0.3 GitHub Action instead of a manual installation script. Corresponding documentation was updated to describe the new approach, clarifying the use of the shared action for coverage upload and verification.

Changes

File(s) Change Summary
.github/workflows/ci.yml Replaced manual CodeScene CLI installation and upload with a shared GitHub Action step.
docs/codescene-cli.md Updated documentation to reflect use of the shared GitHub Action for CodeScene coverage upload.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant GitHub Actions Runner
    participant Leynos Shared Action
    participant CodeScene

    Developer->>GitHub Actions Runner: Push code / trigger CI
    GitHub Actions Runner->>Leynos Shared Action: Invoke upload-codescene-coverage action
    Leynos Shared Action->>CodeScene: Upload coverage data
    CodeScene-->>Leynos Shared Action: Acknowledge upload
    Leynos Shared Action-->>GitHub Actions Runner: Report status
Loading

Possibly related PRs

Suggested reviewers

  • codescene-delta-analysis

Poem

In the warren of CI, scripts once did dwell,
Now a shared Action hops in, doing the job well.
Coverage leaps to CodeScene, swift as a hare,
With checksums in paw, and not a single care.
Docs now reflect this streamlined delight—
All’s well in the pipeline, from morning till night!
🐇✨

✨ Finishing Touches
🧪 Generate Unit Tests
  • Create PR with Unit Tests
  • Post Copyable Unit Tests in Comment
  • Commit Unit Tests in branch codex/use-shared-action-for-ci-workflow

🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai auto-generate unit tests to generate unit tests for this PR.
  • @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.

Copy link
Copy Markdown
Contributor

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

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

Hey @leynos - I've reviewed your changes and they look great!

Prompt for AI Agents
Please address the comments from this code review:
## Individual Comments

### Comment 1
<location> `docs/codescene-cli.md:4` </location>
<code_context>
-The CLI is installed from a remote script published by CodeScene. To ensure the
-integrity of the download, the CI workflow verifies the script using a pinned
-SHA-256 checksum.
+A shared GitHub Action (`leynos/shared-actions/upload-codescene-coverage@v1.0.3`)
+handles downloading and caching the CLI before uploading coverage results. The
+action verifies the installer using a pinned SHA-256 checksum.
</code_context>

<issue_to_address>
This paragraph exceeds the 80 column wrapping limit for paragraphs.

Please wrap this paragraph so that no line exceeds 80 columns, as per the documentation guidelines.
</issue_to_address>

### Comment 2
<location> `docs/codescene-cli.md:5` </location>
<code_context>
-integrity of the download, the CI workflow verifies the script using a pinned
-SHA-256 checksum.
+A shared GitHub Action (`leynos/shared-actions/upload-codescene-coverage@v1.0.3`)
+handles downloading and caching the CLI before uploading coverage results. The
+action verifies the installer using a pinned SHA-256 checksum.

</code_context>

<issue_to_address>
This line is part of a paragraph that exceeds the 80 column wrapping limit.

Ensure that all lines in paragraphs are wrapped to 80 columns or fewer.
</issue_to_address>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Comment thread docs/codescene-cli.md
Comment thread docs/codescene-cli.md
Comment thread .github/workflows/ci.yml Fixed
Copy link
Copy Markdown

@codescene-delta-analysis codescene-delta-analysis Bot left a comment

Choose a reason for hiding this comment

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

Gates Passed
6 Quality Gates Passed

See analysis details in CodeScene

Quality Gate Profile: Pay Down Tech Debt
Want more control? Customize Code Health rules or catch issues early with our IDE extension and CLI tool.

Copy link
Copy Markdown
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: 2

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between aa62f16 and f815678.

📒 Files selected for processing (2)
  • .github/workflows/ci.yml (1 hunks)
  • docs/codescene-cli.md (1 hunks)
🧰 Additional context used
🪛 GitHub Check: CodeQL
.github/workflows/ci.yml

[warning] 117-117: Unpinned tag for a non-immutable Action in workflow
Unpinned 3rd party Action 'CI' step Uses Step uses 'leynos/shared-actions/upload-codescene-coverage' with ref 'v1.0.3', not a pinned commit hash

⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: build-test (sqlite)
  • GitHub Check: build-test (postgres)
  • GitHub Check: windows-build (sqlite)
🔇 Additional comments (3)
.github/workflows/ci.yml (2)

117-120: Replace manual installer with shared action for coverage upload
The workflow now delegates downloading, caching, verifying, and uploading coverage data to the leynos/shared-actions/upload-codescene-coverage@v1.0.3 action, reducing maintenance overhead in CI.


123-123: Pass checksum via environment variable
Good use of the existing CODESCENE_CLI_SHA256 environment variable to verify the installer’s integrity.

docs/codescene-cli.md (1)

4-6: Update documentation to reflect shared action usage
Great clarification that the CodeScene CLI installation and upload are now handled by the shared leynos/shared-actions/upload-codescene-coverage@v1.0.3 action.

Comment thread .github/workflows/ci.yml Outdated
rm install-cs-coverage-tool.sh
- name: Upload coverage data to CodeScene
run: cs-coverage upload --format "lcov" --metric "line-coverage" "lcov.info"
uses: leynos/shared-actions/upload-codescene-coverage@v1.0.3
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Pin actions to immutable references
Referencing @v1.0.3 is still a mutable tag. For stronger security and reproducibility guarantees, pin this step to a specific commit SHA rather than a semantic version tag.

🧰 Tools
🪛 GitHub Check: CodeQL

[warning] 117-117: Unpinned tag for a non-immutable Action in workflow
Unpinned 3rd party Action 'CI' step Uses Step uses 'leynos/shared-actions/upload-codescene-coverage' with ref 'v1.0.3', not a pinned commit hash

🤖 Prompt for AI Agents
In .github/workflows/ci.yml at line 117, the action is referenced using a
mutable tag @v1.0.3. To improve security and reproducibility, replace the
version tag with the specific commit SHA of the action you want to use. Find the
commit SHA corresponding to v1.0.3 in the action's repository and update the
uses line to reference that SHA instead of the version tag.

Comment thread docs/codescene-cli.md
The CLI is installed from a remote script published by CodeScene. To ensure the
integrity of the download, the CI workflow verifies the script using a pinned
SHA-256 checksum.
A shared GitHub Action (`leynos/shared-actions/upload-codescene-coverage@v1.0.3`)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Pin documentation references to immutable commits
The documentation still cites the mutable tag @v1.0.3. Consider updating it to the exact commit SHA to keep docs in sync with the workflow’s security posture.

🤖 Prompt for AI Agents
In docs/codescene-cli.md at line 4, the GitHub Action reference uses a mutable
tag @v1.0.3. Replace this tag with the exact commit SHA of the action version to
ensure the documentation points to an immutable, fixed version, maintaining
consistency and security alignment with the workflow.

Comment thread .github/workflows/ci.yml Fixed
Copy link
Copy Markdown

@codescene-delta-analysis codescene-delta-analysis Bot left a comment

Choose a reason for hiding this comment

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

Gates Passed
6 Quality Gates Passed

See analysis details in CodeScene

Quality Gate Profile: Pay Down Tech Debt
Want more control? Customize Code Health rules or catch issues early with our IDE extension and CLI tool.

Comment thread .github/workflows/ci.yml
rm install-cs-coverage-tool.sh
- name: Upload coverage data to CodeScene
run: cs-coverage upload --format "lcov" --metric "line-coverage" "lcov.info"
uses: leynos/shared-actions/.github/actions/upload-codescene-coverage@v1

Check warning

Code scanning / CodeQL

Unpinned tag for a non-immutable Action in workflow Medium

Unpinned 3rd party Action 'CI' step
Uses Step
uses 'leynos/shared-actions/.github/actions/upload-codescene-coverage' with ref 'v1', not a pinned commit hash
Copy link
Copy Markdown

@codescene-delta-analysis codescene-delta-analysis Bot left a comment

Choose a reason for hiding this comment

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

Gates Passed
6 Quality Gates Passed

See analysis details in CodeScene

Quality Gate Profile: Pay Down Tech Debt
Want more control? Customize Code Health rules or catch issues early with our IDE extension and CLI tool.

@leynos leynos merged commit 47123a0 into main Jun 20, 2025
6 of 8 checks passed
@leynos leynos deleted the codex/use-shared-action-for-ci-workflow branch June 20, 2025 23:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants