Skip to content

style: format shell script indentation - #631

Merged
shunkakinoki merged 1 commit into
mainfrom
style/format-shell-script-indentation
Jan 20, 2026
Merged

style: format shell script indentation#631
shunkakinoki merged 1 commit into
mainfrom
style/format-shell-script-indentation

Conversation

@shunkakinoki

@shunkakinoki shunkakinoki commented Jan 20, 2026

Copy link
Copy Markdown
Owner

Changes

  • Formatted indentation in scripts/update-local-binaries.sh
  • Formatted indentation in spec/update_local_binaries_spec.sh
  • Updated dotagents submodule

Technical Details

Fixed shell script indentation to use consistent 2-space formatting across all test spec blocks.

Testing

  • Manual review of formatting changes
  • No functional changes to script behavior

Generated with OpenCode by Claude


Summary by cubic

Standardized indentation in scripts/update-local-binaries.sh and its spec to 2 spaces for consistent style and readability. Updated the dotagents submodule; no functional changes.

  • Refactors

    • Normalize case/esac indentation in scripts/update-local-binaries.sh to 2 spaces.
    • Reformat spec/update_local_binaries_spec.sh indentation to match style.
  • Dependencies

    • Update dotagents submodule to the latest revision.

Written for commit 332484a. Summary will update on new commits.

Copilot AI review requested due to automatic review settings January 20, 2026 12:46
@mesa-dot-dev

mesa-dot-dev Bot commented Jan 20, 2026

Copy link
Copy Markdown

You do not have enough credits to review this pull request. Please purchase more credits to continue.

@shunkakinoki shunkakinoki added the refactor Indicates code refactoring and improvements. label Jan 20, 2026
@shunkakinoki
shunkakinoki enabled auto-merge (squash) January 20, 2026 12:47
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @shunkakinoki, 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 primarily focuses on enhancing the code style and consistency of shell scripts by standardizing indentation. The changes ensure that both the main script and its corresponding test specifications adhere to a consistent 2-space formatting, improving overall readability and maintainability. Additionally, a submodule has been updated to its most recent version.

Highlights

  • Code Style Consistency: Standardized indentation in scripts/update-local-binaries.sh to use consistent 2-space formatting.
  • Test Spec Indentation: Applied consistent 2-space indentation to all test spec blocks within spec/update_local_binaries_spec.sh for improved readability.
  • Submodule Update: Updated the dotagents Git submodule to its latest commit.
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.

@mesa-dot-dev

mesa-dot-dev Bot commented Jan 20, 2026

Copy link
Copy Markdown

Mesa Description

TL;DR

Standardized shell script indentation to 2 spaces across scripts/update-local-binaries.sh and spec/update_local_binaries_spec.sh.

What changed?

  • Formatted indentation in scripts/update-local-binaries.sh
  • Formatted indentation in spec/update_local_binaries_spec.sh
  • Updated dotagents submodule

Description generated by Mesa. Update settings

@coderabbitai

coderabbitai Bot commented Jan 20, 2026

Copy link
Copy Markdown

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Summary by CodeRabbit

  • Style

    • Improved code formatting and indentation across project files.
  • Chores

    • Updated internal dependencies.

✏️ Tip: You can customize this high-level summary in your review settings.

Walkthrough

This PR updates a submodule pointer and applies whitespace and indentation adjustments to shell scripts. No functional logic changes or behavioral modifications are introduced across any files.

Changes

Cohort / File(s) Summary
Submodule update
dotagents
Submodule reference updated to a new commit (e979c8aa); no code behavior changes
Shell script formatting
scripts/update-local-binaries.sh, spec/update_local_binaries_spec.sh
Indentation and whitespace adjustments only; no functional logic or control flow modifications

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 Hops through indented files so fine,
Whitespace aligned in perfect line!
A submodule springs to newer ground,
Where formatting and order abound!
Twitches nose — all clean and neat! ✨

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch style/format-shell-script-indentation

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

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

@shunkakinoki
shunkakinoki disabled auto-merge January 20, 2026 12:48
@shunkakinoki
shunkakinoki merged commit b302fab into main Jan 20, 2026
25 of 27 checks passed
@shunkakinoki
shunkakinoki deleted the style/format-shell-script-indentation branch January 20, 2026 12:48

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

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.

Code Review

This pull request aims to standardize shell script indentation and also updates the dotagents submodule. While the formatting changes in spec/update_local_binaries_spec.sh are consistent, the change in scripts/update-local-binaries.sh introduces a formatting issue in a case statement. I've added a comment with a suggestion to correct the indentation to align with standard shell scripting practices.

Comment on lines +52 to +55
"$ghq_root"/*)
echo "${repo_dir#"$ghq_root/"}"
return 0
;;

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.

medium

The pattern in a case statement should be indented relative to the case keyword. In this change, the pattern "$ghq_root"/*) is at the same indentation level as case, which is unconventional and reduces code readability. Please indent the pattern and its corresponding block to follow standard shell script formatting.

Suggested change
"$ghq_root"/*)
echo "${repo_dir#"$ghq_root/"}"
return 0
;;
"$ghq_root"/*)
echo "${repo_dir#\"$ghq_root/\"}"
return 0
;;

@cubic-dev-ai cubic-dev-ai Bot left a comment

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.

No issues found across 3 files

Copilot AI left a comment

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.

Pull request overview

This PR standardizes shell script indentation to use consistent 2-space formatting across test specifications and main script code.

Changes:

  • Reformatted all test blocks in spec/update_local_binaries_spec.sh to remove nested indentation
  • Fixed case statement indentation in scripts/update-local-binaries.sh to align with 2-space standard
  • Updated dotagents submodule reference

Reviewed changes

Copilot reviewed 1 out of 3 changed files in this pull request and generated no comments.

File Description
spec/update_local_binaries_spec.sh Removed nested indentation from all It, When, End, setup, cleanup, Before, and After blocks to achieve flat 2-space formatting
scripts/update-local-binaries.sh Adjusted case statement branch indentation from 4 spaces to 2 spaces
dotagents Updated submodule commit reference

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

refactor Indicates code refactoring and improvements.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants