feat: disable atuin shell integration by default

[castrojo]

Summary

Disables atuin shell integration by default in bluefin-cli while keeping the atuin binary installed via Homebrew.

Changes

• Commented out atuin initialization in bling.sh (bash/zsh)
• Commented out atuin initialization in bling.fish
• Added clear documentation explaining the change
• Provided instructions for users who want to re-enable shell integration

Rationale

Users can still access atuin commands manually, but the shell integration (up-arrow and ctrl-r hijacking) is now opt-in rather than opt-out.

Testing

• The atuin binary remains in cli.Brewfile and will be installed
• Shell integration is disabled by default
• Users can uncomment the line to re-enable if desired

[gemini-code-assist]

Summary of Changes

Hello @castrojo, 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 shifts the default behavior of Atuin's shell integration from an opt-out model to an opt-in model. The core Atuin binary remains installed and accessible, but its automatic shell integration features are now commented out by default, allowing users to explicitly enable them if desired. This change aims to provide users with greater control over their shell environment's initial configuration.

Highlights

• Default Behavior Change: Atuin shell integration is now disabled by default in bluefin-cli.
• Atuin Binary Availability: The Atuin binary remains installed via Homebrew and is available for manual use.
• Opt-in Integration: Shell integration features like up-arrow and Ctrl-R hijacking are now opt-in, giving users more control.
• Documentation: Clear documentation has been added to bling.sh and bling.fish explaining the change and providing instructions on how to re-enable shell integration.

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

[dosubot]

Related Documentation

Checked 14 published document(s) in 1 knowledge base(s). No updates required.

^{How did I do? Any feedback?}  

[gemini-code-assist]

Code Review

This pull request disables atuin shell integration by default in bling.sh and bling.fish, making it an opt-in feature. The changes correctly comment out the initialization lines and add instructions for users who wish to re-enable it. My feedback focuses on improving the new comments to retain important contextual information that was present before, such as the correct initialization order relative to starship and instructions for customizing atuin's behavior. This will help users avoid potential misconfigurations.