fix (actions) remove no supported --no-compress argument

[chinchala]

This PR fixes a GitHub Actions bug where passing compress: false incorrectly added the --no-compress argument, which is not a supported flag.
The logic is now corrected so that the --compress argument is added only when compress: true is provided.

[gemini-code-assist]

Summary of Changes

Hello @chinchala, I'm Gemini Code Assist¹! 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 resolves an issue within a GitHub Action where an unsupported command-line argument, --no-compress, was being generated due to incorrect conditional logic. The change refines the argument parsing to ensure that the --compress flag is only included when the compress input is set to true, thereby preventing execution errors and ensuring the action behaves as intended regarding compression settings.

Highlights

• Bug Fix: Corrected a GitHub Actions bug where passing compress: false would incorrectly add the unsupported --no-compress argument.
• Argument Handling: The logic for the compress input has been updated to only add the --compress argument when compress: true is explicitly provided.

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

[coderabbitai]

Walkthrough

The GitHub action configuration for repomix was modified to reverse its compress flag behavior. Previously, the action explicitly added a --no-compress flag when compression was disabled; now, it explicitly adds a --compress flag only when compression is enabled, omitting any flag when disabled.

Changes

Cohort / File(s)	Change Summary
Compress flag logic inversion .github/actions/repomix/action.yml	Changed conditional logic to add --compress flag when compress input is "true"; removed explicit --no-compress flag when compress is "false"

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Single file change with straightforward boolean condition inversion
• No external dependencies or side effects introduced
• Clear, self-contained logic modification

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: fixing the removal of an unsupported --no-compress argument in GitHub Actions.
Description check	✅ Passed	The description clearly explains the bug fix and the corrected logic, though it does not include the checklist items from the repository template.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a63546b and 2656e6b.

📒 Files selected for processing (1)

• .github/actions/repomix/action.yml (1 hunks)

🔇 Additional comments (1)

.github/actions/repomix/action.yml (1)

78-80: Fix is correct: compress flag now added only when explicitly enabled.

The revised logic properly addresses the issue. When compress is "true", the --compress flag is added; when "false" or any other value, no flag is added, allowing repomix to use its default behavior. This avoids passing the unsupported --no-compress argument.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Code Review

This pull request correctly fixes a bug in the GitHub Action where an unsupported --no-compress argument was being passed. The logic is now updated to only include the --compress flag when the compress input is true. The change is concise, accurate, and effectively resolves the issue. Well done.

[yamadashy]

Hi @chinchala !
Thank you for the PR!

I completely missed this issue during implementation.

The changes look good, so I'll merge this! Feel free to contribute again!

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.68%. Comparing base (a63546b) to head (2656e6b).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #965   +/-   ##
=======================================
  Coverage   89.68%   89.68%           
=======================================
  Files         111      111           
  Lines        7843     7843           
  Branches     1504     1504           
=======================================
  Hits         7034     7034           
  Misses        809      809           

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