Skip to content

Conversation

@dlabrecq
Copy link
Contributor

@dlabrecq dlabrecq commented Nov 14, 2025

Clean up release-all script based on PR review

Summary by Sourcery

Enhancements:

  • Refactor release-all script to use boolean flags for appEnv and clouddotEnv and simplify environment argument assignments

@dlabrecq dlabrecq requested a review from a team as a code owner November 14, 2025 00:09
@sourcery-ai
Copy link

sourcery-ai bot commented Nov 14, 2025

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Refactored the release-all script to replace nested appEnv/clouddotEnv checks with boolean flags and flat, targeted assignments for HCCM and ROS stage/prod arguments.

Flow diagram for refactored environment argument assignment in release-all script

flowchart TD
    A["User selects appEnv and clouddotEnv"] --> B["Set DEBUG env variable"]
    B --> C["isHccm = appEnv is 'koku-ui-hccm' or 'all'"]
    B --> D["isRos = appEnv is 'koku-ui-ros' or 'all'"]
    B --> E["isStage = clouddotEnv is 'stage' or 'all'"]
    B --> F["isProd = clouddotEnv is 'prod' or 'all'"]
    C --> G["If isHccm and isStage, set HCCM_STAGE_ARG = '-s'"]
    C --> H["If isHccm and isProd, set HCCM_PROD_ARG = '-p'"]
    D --> I["If isRos and isStage, set ROS_STAGE_ARG = '-q'"]
    D --> J["If isRos and isProd, set ROS_PROD_ARG = '-r'"]
Loading

File-Level Changes

Change Details Files
Introduced boolean flags for environment and stage
  • Added isHccm, isRos, isStage, and isProd variables based on inputs
scripts/release-all.js
Flattened argument assignment logic
  • Replaced nested if/else branches with individual if checks for each env/stage combination
  • Removed redundant 'all' cases inside nested blocks
scripts/release-all.js

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

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @dlabrecq, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on enhancing the clarity and structure of the release-all script. By simplifying the conditional logic for environment variable assignment, the script becomes more straightforward to comprehend and manage, directly addressing feedback from a previous review.

Highlights

  • Refactored Conditional Logic: The setConfig function in scripts/release-all.js has been refactored to improve readability and maintainability. The previous nested if/else if statements for setting environment variables based on appEnv and clouddotEnv have been replaced.
  • Introduced Helper Variables: New boolean variables (isHccm, isRos, isStage, isProd) were introduced to clearly define the conditions for setting specific process.env variables, simplifying the logic flow.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@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 there - I've reviewed your changes - here's some feedback:

  • Consider refactoring the repeated if blocks by using a data-driven mapping (e.g. { HCCM: {stage: '-s', prod: '-p'}, ROS: {stage: '-q', prod: '-r'} }) and iterating through it to reduce duplication and improve maintainability.
  • Add explicit validation or a default case for unexpected appEnv or clouddotEnv values to avoid silently skipping flag assignments.
  • Before setting new vars, you may want to clear any existing HCCM_ARG and ROS_ARG values so you don’t carry over stale flags between runs.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- Consider refactoring the repeated if blocks by using a data-driven mapping (e.g. { HCCM: {stage: '-s', prod: '-p'}, ROS: {stage: '-q', prod: '-r'} }) and iterating through it to reduce duplication and improve maintainability.
- Add explicit validation or a default case for unexpected appEnv or clouddotEnv values to avoid silently skipping flag assignments.
- Before setting new vars, you may want to clear any existing HCCM_*_ARG and ROS_*_ARG values so you don’t carry over stale flags between runs.

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.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request refactors the logic for setting environment variables in the release-all.js script, making it much cleaner and easier to understand by removing nested conditional statements. The change is a significant improvement. I've added one suggestion to further improve maintainability by using a data-driven approach, which would reduce code duplication and make future changes simpler.

@codecov
Copy link

codecov bot commented Nov 14, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.82%. Comparing base (c16f86b) to head (5d41ad4).
⚠️ Report is 5 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #4645   +/-   ##
=======================================
  Coverage   88.82%   88.82%           
=======================================
  Files         480      480           
  Lines        9075     9075           
  Branches     2197     2198    +1     
=======================================
  Hits         8061     8061           
- Misses        953      954    +1     
+ Partials       61       60    -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@dlabrecq dlabrecq merged commit 7a8ac69 into project-koku:main Nov 14, 2025
9 checks passed
@dlabrecq dlabrecq deleted the next4 branch November 14, 2025 01:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant