Fix coverage action env variables

[leynos]

Summary

• derive CodeScene coverage CLI environment from action inputs
• document the change in the action changelog

Testing

• npm test (fails: package.json not found)

---

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

Summary by Sourcery

Derive the CodeScene coverage action’s environment variables from inputs to prevent load failures caused by unsupported secrets or vars expressions, and document the change in a new v1.5.1 CHANGELOG entry.

Enhancements:

• Derive environment variables CS_ACCESS_TOKEN and CODESCENE_CLI_SHA256 from action inputs to avoid unsupported secrets or vars expressions.

Documentation:

• Add v1.5.1 entry to the action CHANGELOG documenting the environment variable derivation fix.

Summary by CodeRabbit

• Documentation
  • Added a changelog entry for version 1.5.1, clarifying how environment variables are derived from action inputs.
  • Updated comments in the GitHub Actions workflow to explain environment variable handling for composite actions.

[sourcery-ai]

Reviewer's Guide

This PR clarifies and documents how the CodeScene coverage action derives its CS_ACCESS_TOKEN and CODESCENE_CLI_SHA256 environment variables from user inputs, preventing failures when accessing unsupported secrets or vars expressions.

File-Level Changes

Change	Details	Files
Document new v1.5.1 release with input-based env var derivation	Append v1.5.1 section to changelog Describe that CS_ACCESS_TOKEN and CODESCENE_CLI_SHA256 come from inputs to avoid unsupported expressions	.github/actions/upload-codescene-coverage/CHANGELOG.md
Annotate action.yml to highlight env var derivation	Insert inline comment explaining that actions can’t access secrets or vars Emphasize that environment variables are mapped from inputs	.github/actions/upload-codescene-coverage/action.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

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Warning

Rate limit exceeded

@leynos has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 1 minutes and 18 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between df660b0 and 51d4f0c.

📒 Files selected for processing (2)

• .github/actions/upload-codescene-coverage/CHANGELOG.md (1 hunks)
• .github/actions/upload-codescene-coverage/action.yml (1 hunks)

Walkthrough

This change updates the upload-codescene-coverage GitHub Action by adding a changelog entry for version 1.5.1 and inserting a clarifying comment in the action YAML. The updates document and explain how environment variables are now explicitly derived from action inputs to prevent unsupported expression errors.

Changes

File(s)	Change Summary
.github/actions/upload-codescene-coverage/CHANGELOG.md	Added a changelog entry for version 1.5.1 detailing explicit derivation of environment variables.
.github/actions/upload-codescene-coverage/action.yml	Added a comment clarifying environment variable derivation from inputs in the composite action.

Possibly related PRs

• Fix upload-codescene-coverage env #7: Fixes environment variable handling in the same action by deriving them from inputs, addressing similar configuration issues.
• Update coverage workflow mxd#194: Switches the coverage workflow to use the updated shared action, involving the same environment variable handling.
• Add upload-codescene-coverage action #1: Introduces the initial implementation of the upload-codescene-coverage action, which is further clarified in this PR.

Poem

The changelog grows, a note appears,
About environment woes and action fears.
Now variables from inputs are clearly derived,
So composite actions load, no longer deprived.
With a hop and a skip, this bunny approves—
Clearer code makes for smoother moves!
🐇✨

✨ Finishing Touches

🧪 Generate Unit Tests

• Create PR with Unit Tests
• Post Copyable Unit Tests in Comment
• Commit Unit Tests in branch codex/fix-coverage-action-template-validation-errors

---

🪧 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.

[sourcery-ai]

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

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}