Skip to content

Switch to shared CI actions#79

Merged
leynos merged 3 commits intomainfrom
codex/update-ci-workflow-with-shared-actions
Jun 21, 2025
Merged

Switch to shared CI actions#79
leynos merged 3 commits intomainfrom
codex/update-ci-workflow-with-shared-actions

Conversation

@leynos
Copy link
Copy Markdown
Owner

@leynos leynos commented Jun 21, 2025

Summary

  • use Leynos shared action for Rust toolchain setup and caching
  • upload coverage to CodeScene with shared action

Testing

  • cargo fmt --all -- --check
  • cargo clippy --all-targets --all-features -- -D warnings
  • cargo test

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

Summary by Sourcery

Migrate CI workflow to use Leynos shared GitHub actions for Rust setup, caching, and CodeScene coverage upload

CI:

  • Replace manual Rust toolchain installation and caching with leynos/shared-actions setup-rust action
  • Replace custom CodeScene CLI installation and upload commands with leynos/shared-actions upload-codescene-coverage action

Summary by CodeRabbit

  • Chores
    • Updated the CI workflow to use custom actions for Rust setup and CodeScene coverage upload, streamlining the process and removing manual installation and caching steps.

@sourcery-ai
Copy link
Copy Markdown
Contributor

sourcery-ai Bot commented Jun 21, 2025

Reviewer's Guide

Replaces custom CI steps for Rust toolchain setup and coverage upload with shared Leynos actions to streamline and standardize the workflow.

File-Level Changes

Change Details Files
Switch Rust toolchain installation and caching to the shared setup action
  • Removed manual Rust installation step
  • Dropped cargo registry and build caches
  • Added leynos/shared-actions setup-rust action
.github/workflows/ci.yml
Use shared action for uploading coverage to CodeScene
  • Removed manual download and install of the CodeScene CLI
  • Replaced direct cs-coverage upload command
  • Added leynos/shared-actions upload-codescene-coverage action with parameters
.github/workflows/ci.yml

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 21, 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 was updated to use custom shared GitHub Actions for Rust toolchain setup (including caching) and CodeScene coverage upload. Manual steps for installing Rust, managing caches, installing CodeScene, and uploading coverage were removed in favour of these composite actions. No changes were made to exported or public code entities.

Changes

File(s) Change Summary
.github/workflows/ci.yml Replaced manual Rust toolchain setup, caching, and CodeScene coverage upload with shared custom actions. Removed explicit toolchain/component installation, cache management, and shell-based CodeScene steps.

Sequence Diagram(s)

sequenceDiagram
    participant GitHub Actions
    participant Setup Rust Action
    participant Upload Coverage Action

    GitHub Actions->>Setup Rust Action: Run leynos/shared-actions/.github/actions/setup-rust@v1
    Setup Rust Action-->>GitHub Actions: Rust toolchain ready (with caching)
    GitHub Actions->>Upload Coverage Action: Run leynos/shared-actions/.github/actions/upload-codescene-coverage@v1 (format: lcov)
    Upload Coverage Action-->>GitHub Actions: Coverage uploaded
Loading

Possibly related PRs

Suggested reviewers

  • codescene-delta-analysis

Poem

In the warren where workflows run,
The old steps have hopped and gone!
Now actions shared do all the toil,
Setting up Rust and checking the soil.
Coverage leaps to CodeScene’s den,
The CI’s clean—let’s hop again! 🐇

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

🪧 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 - here's some feedback:

  • Confirm that the shared setup-rust@v1 action still provides the same cargo registry and target caching you previously had to avoid slower CI runs.
  • Consider pinning your shared-actions references to a specific commit SHA or more precise version tag rather than the floating v1, for greater build reproducibility.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- Confirm that the shared `setup-rust@v1` action still provides the same cargo registry and target caching you previously had to avoid slower CI runs.
- Consider pinning your shared-actions references to a specific commit SHA or more precise version tag rather than the floating `v1`, for greater build reproducibility.

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 .github/workflows/ci.yml Fixed
Comment thread .github/workflows/ci.yml Fixed
Comment thread .github/workflows/ci.yml Fixed
Comment thread .github/workflows/ci.yml
restore-keys: |
${{ runner.os }}-cargo-${{ env.BUILD_PROFILE }}-
- name: Setup Rust
uses: leynos/shared-actions/.github/actions/setup-rust@v1.1.0

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/setup-rust' with ref 'v1.1.0', not a pinned commit hash
Comment thread .github/workflows/ci.yml


if: secrets.CS_ACCESS_TOKEN
uses: leynos/shared-actions/.github/actions/upload-codescene-coverage@v1.1.0

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.1.0', not a pinned commit hash
@leynos leynos merged commit a5af436 into main Jun 21, 2025
4 checks passed
@leynos leynos deleted the codex/update-ci-workflow-with-shared-actions branch June 21, 2025 09:20
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