Skip to content

Fix border, tool select & more explanation - #4

Merged
fank merged 7 commits into
mainfrom
jd_more_explanation
Jan 8, 2026
Merged

fank merged 7 commits into
mainfrom
jd_more_explanation

Conversation

@smini-digital

@smini-digital smini-digital commented Dec 30, 2025 •

Copy link
Copy Markdown
Contributor

Belongs to: enthus-appdev/atl-cli#16

✅ Header alignment - Fixed issues in the CLI banner
✅ Python f-string escaping - Fixed shell script parse errors by using \\" instead of \"
✅ Dynamic column alignment - Replaced hardcoded 12-char padding with tab-separated values + column -t for consistency with jq
✅ Checkbox validation - Added validation to prevent empty selections in the tool selector -> Menu vanished without warning when used through https://github.com/enthus-appdev/environment-setup

-> Bump version in https://github.com/enthus-appdev after merge like https://github.com/enthus-appdev/environment-setup/commit/82a5333105f6b528cc533c0465834bd01392abde

@smini-digital smini-digital self-assigned this Dec 30, 2025
@gemini-code-assist

Copy link
Copy Markdown

Summary of Changes

Hello @smini-digital, 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 enhances the user experience of the CLI tool by refining the visual presentation of its header banner and improving the clarity of error messages. Specifically, it addresses an issue with banner alignment and provides more actionable advice to users encountering package manager detection problems during sqlcmd installation.

Highlights

  • CLI Header Banner Improvement: The header banner in bin/cli.js has been refactored to ensure consistent border alignment and better readability, making the CLI's initial display more polished.
  • Enhanced SQLCMD Installation Guidance: The error message for sqlcmd installation in lib/installers/sqlcmd.js now provides a more helpful suggestion to install Homebrew, including a direct link, when no supported package manager is detected.
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. ↩

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

Copy link
Copy Markdown

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 addresses a display issue with the header banner by reconstructing it line-by-line, and improves the user guidance when a package manager is not detected. The header implementation, while functional, is overly complex and can be simplified for better readability. The clarification in the sqlcmd installer is a helpful addition for users.

Comment thread bin/cli.js Outdated
@smini-digital smini-digital changed the title Fix border & more explanation Fix border, tool select & more explanation Dec 30, 2025
@smini-digital

Copy link
Copy Markdown
Contributor Author

/gemini review

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

Copy link
Copy Markdown

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 introduces several useful improvements. The header banner rendering is now more robust, and the tool selection prompt now correctly validates that at least one tool is selected, improving the user experience. The error message for a missing package manager is also more helpful. The fixes for escaping quotes in the embedded Python scripts are correct. I've added a couple of suggestions to improve the formatting logic in the Python fallback code to make it more robust and consistent with the primary jq implementation.

Comment thread lib/installers/sqlcmd.js Outdated
Comment thread lib/installers/sqlcmd.js Outdated
@smini-digital
smini-digital marked this pull request as ready for review December 30, 2025 13:01
@smini-digital
smini-digital requested review from Hinne1 and fank December 30, 2025 13:09
The top and bottom borders were hardcoded while boxWidth was only
used for inner content. Now both use the same variable for consistency.
@fank
fank merged commit 9ec5fa2 into main Jan 8, 2026
@fank
fank deleted the jd_more_explanation branch January 8, 2026 10:42
fank added a commit that referenced this pull request Apr 11, 2026
runConfig threw errors containing the full args joined — for
`config set contexts.X.grafana.password <value>` that embedded the
plaintext password in error.message, which was then logged by the
outer catch handler.

Add a redactSensitiveArgs helper that replaces any value whose
preceding key matches .token / .password / .secret / .apikey with
<redacted> before building the error message.

Addresses CodeQL alert #4 (js/clear-text-logging, error severity).
@fank fank mentioned this pull request Apr 11, 2026
2 of 3 tasks
fank added a commit that referenced this pull request Apr 11, 2026
* ci: set explicit contents: read permissions on workflows

Addresses CodeQL alerts #1, #3, #9 (actions/missing-workflow-permissions).
Both workflows only need read access to the repo contents, so the minimal
permissions block is set at the workflow level.

* fix: use exact-match check for git SSH rewrite config value

The installers were using .includes('https://github.com/') to check the
output of `git config --get url.git@github.com:.insteadOf`. That output
is either empty or exactly the value we set ourselves, so exact match
is both more correct and silences CodeQL's
js/incomplete-url-substring-sanitization rule.

Addresses CodeQL alerts #5, #6, #7, #8 across atl, discord, esq, and
n8n installers.

* fix(grafanactl): redact secrets from runConfig error messages

runConfig threw errors containing the full args joined — for
`config set contexts.X.grafana.password <value>` that embedded the
plaintext password in error.message, which was then logged by the
outer catch handler.

Add a redactSensitiveArgs helper that replaces any value whose
preceding key matches .token / .password / .secret / .apikey with
<redacted> before building the error message.

Addresses CodeQL alert #4 (js/clear-text-logging, error severity).
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.

2 participants