Skip to content

Fix CodeScene token duplication#132

Closed
leynos wants to merge 1 commit intomainfrom
codex/remove-redundant-env-block-and-unused-id
Closed

Fix CodeScene token duplication#132
leynos wants to merge 1 commit intomainfrom
codex/remove-redundant-env-block-and-unused-id

Conversation

@leynos
Copy link
Copy Markdown
Owner

@leynos leynos commented Jul 29, 2025

Summary

  • clean up CodeScene step envs
  • drop unused step id in CI

Testing

  • make fmt
  • make lint
  • make test
  • make markdownlint
  • make nixie (fails: error: too many arguments. Expected 0 arguments but got 1)

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

Summary by Sourcery

Clean up CI workflow by removing redundant step id and environment settings for CodeScene coverage upload

CI:

  • Remove unused 'id: generate-coverage' from the coverage generation step
  • Drop explicit CS_ACCESS_TOKEN environment block from the CodeScene upload step

@sourcery-ai
Copy link
Copy Markdown
Contributor

sourcery-ai Bot commented Jul 29, 2025

Reviewer's Guide

The PR cleans up the CI workflow by removing an unused step identifier and eliminating a redundant CodeScene access token environment block in the coverage upload step.

File-Level Changes

Change Details Files
Removed unused step identifier from coverage generation
  • Dropped the id: generate-coverage line
  • Retained the coverage action invocation without an explicit step ID
.github/workflows/ci.yml
Eliminated redundant CodeScene token environment block
  • Removed the explicit env: CS_ACCESS_TOKEN section
  • Relied on the existing environment variable check in the upload step
.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 Jul 29, 2025

Summary by CodeRabbit

  • Chores
    • Improved workflow configuration by removing redundant environment variable declarations and simplifying step identifiers in the CI process.

Walkthrough

Remove the explicit id: generate-coverage from the coverage generation step and eliminate the redundant CS_ACCESS_TOKEN environment variable declaration in the CodeScene coverage upload step within .github/workflows/ci.yml. Rely on the job-level environment variable for CS_ACCESS_TOKEN. The conditional logic for uploading coverage remains unchanged.

Changes

Cohort / File(s) Change Summary
CI Workflow Coverage Upload Simplification
.github/workflows/ci.yml
Remove explicit step ID from coverage generation, delete redundant CS_ACCESS_TOKEN env declaration in upload step, rely on job-level env variable, retain conditional upload logic.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Poem

Streamline the workflow, tidy and neat,
Redundant lines now face defeat.
Tokens set once, no need to repeat,
Coverage uploads skip a beat.
In CI’s dance, less is more—
Simpler scripts we all adore!
🛠️✨


📜 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 35b50b8 and fc92d16.

📒 Files selected for processing (1)
  • .github/workflows/ci.yml (1 hunks)
🔇 Additional comments (2)
.github/workflows/ci.yml (2)

21-21: Eliminate redundant environment override.

Removal of the step-level CS_ACCESS_TOKEN prevents secret shadowing and relies on the job-level variable. Change is correct.


21-31: Remove id: generate-coverage safely

No occurrences of steps.generate-coverage.outputs or generate-coverage found across the repository.
All downstream references validated—no changes required.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch codex/remove-redundant-env-block-and-unused-id

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

  • Removing the env block for CS_ACCESS_TOKEN means the upload step will never receive the secret—either re-inject the secret via env or change the if condition to reference secrets.CS_ACCESS_TOKEN directly.
  • You dropped the id from the generate-coverage step—make sure no downstream steps or workflows are still referring to steps.generate-coverage outputs.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- Removing the env block for CS_ACCESS_TOKEN means the upload step will never receive the secret—either re-inject the secret via env or change the if condition to reference secrets.CS_ACCESS_TOKEN directly.
- You dropped the id from the generate-coverage step—make sure no downstream steps or workflows are still referring to steps.generate-coverage outputs.

## Individual Comments

### Comment 1
<location> `.github/workflows/ci.yml:27` </location>
<code_context>
           output-path: lcov.info
           format: lcov
       - name: Upload coverage data to CodeScene
-        env:
-          CS_ACCESS_TOKEN: ${{ secrets.CS_ACCESS_TOKEN }}
         if: ${{ env.CS_ACCESS_TOKEN != '' }}
         uses: leynos/shared-actions/.github/actions/upload-codescene-coverage@v1.2.1
</code_context>

<issue_to_address>
Removing the explicit 'env' block may affect environment variable availability.

Please verify that 'CS_ACCESS_TOKEN' is still accessible to the 'upload-codescene-coverage' action after removing the explicit 'env' block.
</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/workflows/ci.yml
Comment on lines -27 to -28
env:
CS_ACCESS_TOKEN: ${{ secrets.CS_ACCESS_TOKEN }}
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.

issue (bug_risk): Removing the explicit 'env' block may affect environment variable availability.

Please verify that 'CS_ACCESS_TOKEN' is still accessible to the 'upload-codescene-coverage' action after removing the explicit 'env' block.

@leynos leynos closed this Jul 29, 2025
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