Fix env block in upload-codescene-coverage action

[leynos]

Summary

• export env vars in a step instead of using unsupported env under runs
• update docs and changelog for upload-codescene-coverage action

Testing

• npm test (fails: Could not read package.json)

---

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

Summary by Sourcery

Fix the env block in the composite action by exporting CS_ACCESS_TOKEN and CODESCENE_CLI_SHA256 via an initial setup step and update related documentation.

Bug Fixes:

• Remove unsupported env block from the runs section of the upload-codescene-coverage action
• Export access-token and installer-checksum inputs to GITHUB_ENV for use in later steps

Documentation:

• Update README to describe the new environment variable export step
• Add a v1.5.2 entry to CHANGELOG detailing the removal of the env block and addition of the export step

Summary by CodeRabbit

• Documentation

  • Improved clarity in the documentation regarding how environment variables are exported for use in later steps.
  • Added a changelog entry for the latest update.

• Chores

  • Updated the workflow to export environment variables through a dedicated setup step rather than directly in the configuration.

[sourcery-ai]

Reviewer's Guide

This PR replaces the unsupported env block under the runs section with an explicit setup step that exports required inputs into GITHUB_ENV, and updates documentation and the changelog to reflect this change.

Flow diagram for environment variable export in upload-codescene-coverage action

flowchart TD
    A[Action starts] --> B[Export env for later steps]
    B -->|echo CS_ACCESS_TOKEN and CODESCENE_CLI_SHA256 to $GITHUB_ENV| C[Validate inputs]
    C --> D[Subsequent steps use exported env vars]

Loading

File-Level Changes

Change	Details	Files
Move env var configuration to a setup step using GITHUB_ENV	Remove the env block under runs Add a step that echoes access-token and installer-checksum into GITHUB_ENV Specify bash as the shell for the export step	.github/actions/upload-codescene-coverage/action.yml
Update README to reflect new env export method	Reword environment section to describe export via setup step Remove references to env block under runs Clarify that inputs become available for later steps	.github/actions/upload-codescene-coverage/README.md
Revise CHANGELOG with version bump and export step notes	Add a new v1.5.2 entry Document removal of unsupported env block Note the addition of the explicit export step	.github/actions/upload-codescene-coverage/CHANGELOG.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

• 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]

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

This change updates the upload-codescene-coverage GitHub Action by removing unsupported environment variable declarations from the runs section and introducing a dedicated step to export required variables using $GITHUB_ENV. Documentation is updated for clarity, and a changelog entry for version 1.5.2 is added.

Changes

File(s)	Summary
.github/actions/upload-codescene-coverage/action.yml	Removed env block from runs; added explicit step to export environment variables via $GITHUB_ENV.
.github/actions/upload-codescene-coverage/README.md	Reworded documentation for clarity on how environment variables are exported for later steps.
.github/actions/upload-codescene-coverage/CHANGELOG.md	Added changelog entry for version 1.5.2 documenting the environment variable export method change.

Sequence Diagram(s)

sequenceDiagram
    participant Workflow
    participant Action
    participant $GITHUB_ENV

    Workflow->>Action: Invoke upload-codescene-coverage
    Action->>$GITHUB_ENV: Export CS_ACCESS_TOKEN and CODESCENE_CLI_SHA256
    Action->>Workflow: Subsequent steps access exported env vars

Loading

Possibly related PRs

• Fix coverage action env variables #10: Also modifies how CS_ACCESS_TOKEN and CODESCENE_CLI_SHA256 are handled in the same GitHub Action, focusing on their export and availability.
• Fix upload-codescene-coverage env #7: An earlier fix related to environment variable export in the same action, which this PR further refines.
• Fix upload-codescene-coverage env #9: Introduced the relevant inputs and initial environment variable setup, directly preceding the changes in this PR.

Poem

🐇
Hop, hop, the action’s clean,
No more env blocks to be seen!
With exports set and docs anew,
Our coverage hops right through.
Changelog grows, the steps align—
GitHub Actions, running fine!

✨ Finishing Touches

🧪 Generate Unit Tests

• Create PR with Unit Tests
• Post Copyable Unit Tests in Comment
• Commit Unit Tests in branch codex/fix-invalid--env--block-in-composite-action

---

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

[coderabbitai]

Actionable comments posted: 1

🔭 Outside diff range comments (1)

.github/actions/upload-codescene-coverage/CHANGELOG.md (1)

43-47: Grammar nit – insert missing article

Consider:

- Remove the unsupported `env` block from the `runs` section.

Tiny copy polish for consistency with earlier entries.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 389e772 and 3ff5d41.

📒 Files selected for processing (3)

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

🧰 Additional context used

🪛 LanguageTool

.github/actions/upload-codescene-coverage/CHANGELOG.md

[uncategorized] ~45-~45: You might be missing the article “the” here.
Context: ...vars expressions. ## v1.5.2 - Remove unsupported env block from the runs section. - ...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)

🔇 Additional comments (1)

.github/actions/upload-codescene-coverage/README.md (1)

21-22: Wording update is clear and accurate

The revised sentence succinctly describes the export mechanism and matches the action implementation.