Skip to content

Fix upload-codescene-coverage env#7

Merged
leynos merged 2 commits intomainfrom
codex/fix-issues-in-upload-codescene-coverage-action
Jun 21, 2025
Merged

Fix upload-codescene-coverage env#7
leynos merged 2 commits intomainfrom
codex/fix-issues-in-upload-codescene-coverage-action

Conversation

@leynos
Copy link
Copy Markdown
Owner

@leynos leynos commented Jun 21, 2025

Summary

  • remove invalid env section from the action
  • document the required env vars in the README
  • document caching details like in setup-rust
  • note fix in CHANGELOG

Testing

  • true

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

Summary by Sourcery

Fix action load failure by removing unsupported environment references, enrich README with environment variable and caching documentation, and update CHANGELOG with recent releases

Bug Fixes:

  • Remove unsupported secrets and vars references from action.yml to fix action load failure

Documentation:

  • Document required CS_ACCESS_TOKEN and CODESCENE_CLI_SHA256 environment variables in README
  • Add caching behavior, limitations, and best practices for the CodeScene Coverage CLI to README
  • Wrap README lines to 80 columns for consistency
  • Add v1.4.2, v1.4.3, and v1.4.4 entries to CHANGELOG

Summary by CodeRabbit

  • Documentation

    • Updated the changelog with recent patch versions, highlighting resolved action load issues and improved documentation.
    • Enhanced the README with detailed sections on required environment variables and caching behaviour, including usage recommendations and best practices.
    • Improved README formatting for better readability.
  • Chores

    • Removed unsupported environment variable references from the action configuration to prevent action load failures.

@sourcery-ai
Copy link
Copy Markdown
Contributor

sourcery-ai Bot commented Jun 21, 2025

Reviewer's Guide

This PR removes an unsupported env block from the GitHub Action, enriches the README with required environment variables and detailed caching guidance (wrapping content to 80 columns), and records these updates in the CHANGELOG with new patch entries.

File-Level Changes

Change Details Files
Remove invalid environment block from action configuration
  • Deleted unsupported env definitions for CS_ACCESS_TOKEN and CODESCENE_CLI_SHA256
  • Prevent action load failures by eliminating secrets and vars references
.github/actions/upload-codescene-coverage/action.yml
Add Environment variables section to README
  • Inserted description of CS_ACCESS_TOKEN and CODESCENE_CLI_SHA256
  • Marked access token as required and checksum as optional
.github/actions/upload-codescene-coverage/README.md
Document caching behavior in README
  • Outlined cache key composition and storage location
  • Described requirements, limitations, and effective use recommendations
.github/actions/upload-codescene-coverage/README.md
Reformat README lines to 80 columns
  • Wrapped existing text and tables to enforce 80-character width
.github/actions/upload-codescene-coverage/README.md
Update CHANGELOG with new patch entries
  • Added v1.4.2 entry for env block removal and docs
  • Added v1.4.3 entry for caching details
  • Added v1.4.4 entry for formatting consistency
.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

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jun 21, 2025

Walkthrough

This update revises the upload-codescene-coverage GitHub Action by removing unsupported environment variable declarations from its configuration and enhancing its documentation. The README now details required environment variables and caching behaviour, while the changelog records these documentation and configuration adjustments. No functional or logic changes were made.

Changes

File(s) Change Summary
.github/actions/upload-codescene-coverage/CHANGELOG.md Added entries for v1.4.2, v1.4.3, and v1.4.4 documenting removal of unsupported env vars and expanded README documentation including formatting improvements.
.github/actions/upload-codescene-coverage/README.md Expanded with sections on required environment variables and detailed caching behaviour, including best practices and formatting adjustments.
.github/actions/upload-codescene-coverage/action.yml Removed CS_ACCESS_TOKEN and CODESCENE_CLI_SHA256 from environment variable declarations in the action configuration.

Possibly related PRs

Poem

In the warren where actions hop and run,
We tidied the code—old env vars are done!
Documentation now clear,
Caching tips appear,
With every commit, our coverage shines like the sun.
🐇✨


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 4bfe6a0 and 9cdc76b.

📒 Files selected for processing (2)
  • .github/actions/upload-codescene-coverage/CHANGELOG.md (1 hunks)
  • .github/actions/upload-codescene-coverage/README.md (3 hunks)
🧰 Additional context used
🪛 LanguageTool
.github/actions/upload-codescene-coverage/README.md

[typographical] ~21-~21: Consider using an em dash in dialogues and enumerations.
Context: ...ironment variables - CS_ACCESS_TOKEN – CodeScene project access token (require...

(DASH_RULE)


[uncategorized] ~46-~46: Use a comma before ‘so’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...ts - CS_ACCESS_TOKEN must be provided so the installer can download the CLI and ...

(COMMA_COMPOUND_SENTENCE_2)


[style] ~48-~48: To form a complete sentence, be sure to include a subject.
Context: ...icate uploads. - CODESCENE_CLI_SHA256 should be set to the published checksum of the...

(MISSING_IT_THERE)


[uncategorized] ~64-~64: Use a comma before ‘so’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...overage file path consistent across jobs so subsequent steps can locate it reliab...

(COMMA_COMPOUND_SENTENCE_2)

🔇 Additional comments (3)
.github/actions/upload-codescene-coverage/CHANGELOG.md (1)

25-34: CHANGELOG entries are complete and consistent
The new sections for v1.4.2, v1.4.3, and v1.4.4 follow the existing format and clearly document the configuration and documentation updates.

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

9-10: Table rows updated correctly
The inputs table rows for path and format are clear and maintain the established format.


37-43: Caching section is well-documented
The new Caching section clearly explains cache key construction, restoration, and saving behaviour.

✨ Finishing Touches
🧪 Generate Unit Tests
  • Create PR with Unit Tests
  • Post Copyable Unit Tests in Comment
  • Commit Unit Tests in branch codex/fix-issues-in-upload-codescene-coverage-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.

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> `.github/actions/upload-codescene-coverage/README.md:65` </location>
<code_context>
+- Pin the installer checksum whenever possible to avoid using a compromised
+  download.
+- Keep your coverage file path consistent across jobs so subsequent steps can
+  locate it reliably.
+
 Release history is available in [CHANGELOG](CHANGELOG.md).
</code_context>

<issue_to_address>
Some added lines in bullets and paragraphs exceed 80 columns.

For example, the line 'The CodeScene Coverage CLI is stored in `~/.local/bin/cs-coverage` and cached with [actions/cache](https://github.com/actions/cache). The cache key combines the runner OS and the CLI version extracted from the installer script. The cache is restored at the start of the job and saved after the job finishes.' is longer than 80 columns. Please wrap paragraphs and bullets to 80 columns as per the instructions.
</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 .github/actions/upload-codescene-coverage/README.md
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: 4

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 1518697 and 4bfe6a0.

📒 Files selected for processing (3)
  • .github/actions/upload-codescene-coverage/CHANGELOG.md (1 hunks)
  • .github/actions/upload-codescene-coverage/README.md (2 hunks)
  • .github/actions/upload-codescene-coverage/action.yml (0 hunks)
💤 Files with no reviewable changes (1)
  • .github/actions/upload-codescene-coverage/action.yml
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
.github/actions/upload-codescene-coverage/CHANGELOG.md

25-25: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)


26-26: Lists should be surrounded by blank lines
null

(MD032, blanks-around-lists)


30-30: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)


31-31: Lists should be surrounded by blank lines
null

(MD032, blanks-around-lists)

🪛 LanguageTool
.github/actions/upload-codescene-coverage/README.md

[typographical] ~21-~21: Consider using an em dash in dialogues and enumerations.
Context: ...ironment variables - CS_ACCESS_TOKEN – CodeScene project access token (require...

(DASH_RULE)


[uncategorized] ~46-~46: Use a comma before ‘so’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...ts - CS_ACCESS_TOKEN must be provided so the installer can download the CLI and ...

(COMMA_COMPOUND_SENTENCE_2)


[style] ~48-~48: To form a complete sentence, be sure to include a subject.
Context: ...icate uploads. - CODESCENE_CLI_SHA256 should be set to the published checksum of the...

(MISSING_IT_THERE)


[uncategorized] ~64-~64: Use a comma before ‘so’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...overage file path consistent across jobs so subsequent steps can locate it reliab...

(COMMA_COMPOUND_SENTENCE_2)

Comment thread .github/actions/upload-codescene-coverage/CHANGELOG.md
Comment thread .github/actions/upload-codescene-coverage/README.md
Comment thread .github/actions/upload-codescene-coverage/README.md
Comment thread .github/actions/upload-codescene-coverage/README.md
@leynos
Copy link
Copy Markdown
Owner Author

leynos commented Jun 21, 2025

@sourcery-ai review

@leynos
Copy link
Copy Markdown
Owner Author

leynos commented Jun 21, 2025

@coderabbitai review

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jun 21, 2025

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

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:

  • The changelog notes using restore keys for caching across minor versions, but the README’s caching section doesn’t document any restore-keys pattern—please either add the restore-keys configuration or update the changelog to match the implementation.
  • Consider including a full example job snippet in the README showing the actions/cache config (including restore-keys fallback) so users can quickly copy a working setup.
  • You might surface the required environment variables in the action metadata (e.g. as inputs) so they appear in the GitHub Actions UI rather than only in the README.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- The changelog notes using restore keys for caching across minor versions, but the README’s caching section doesn’t document any restore-keys pattern—please either add the restore-keys configuration or update the changelog to match the implementation.
- Consider including a full example job snippet in the README showing the actions/cache config (including restore-keys fallback) so users can quickly copy a working setup.
- You might surface the required environment variables in the action metadata (e.g. as inputs) so they appear in the GitHub Actions UI rather than only in the README.

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.

@leynos
Copy link
Copy Markdown
Owner Author

leynos commented Jun 21, 2025

@coderabbitai review

@leynos
Copy link
Copy Markdown
Owner Author

leynos commented Jun 21, 2025

@sourcery-ai review

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jun 21, 2025

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

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:

  • Add explicit input validation in the entrypoint (or action.yml) to error out if CS_ACCESS_TOKEN is unset, so users get a clear message rather than a downstream failure.
  • Consider prefixing your cache key with a static tag (e.g. cs-coverage-cache-) to avoid accidental key collisions when combining OS and CLI version.
  • You could consolidate the separate v1.4.2–v1.4.4 changelog entries into a single cohesive release note to keep the history concise.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- Add explicit input validation in the entrypoint (or action.yml) to error out if CS_ACCESS_TOKEN is unset, so users get a clear message rather than a downstream failure.
- Consider prefixing your cache key with a static tag (e.g. `cs-coverage-cache-`) to avoid accidental key collisions when combining OS and CLI version.
- You could consolidate the separate v1.4.2–v1.4.4 changelog entries into a single cohesive release note to keep the history concise.

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.

@leynos leynos merged commit ee271a8 into main Jun 21, 2025
1 check passed
@leynos leynos deleted the codex/fix-issues-in-upload-codescene-coverage-action branch June 21, 2025 01:16
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.

1 participant