Skip to content

feat(completion-hint): Add a hint prompting the user to add completion to the shell - #201

Open
mohammed-io wants to merge 10 commits into
BunnyWay:mainfrom
mohammed-io:feat/completion-reminder
Open

feat(completion-hint): Add a hint prompting the user to add completion to the shell#201
mohammed-io wants to merge 10 commits into
BunnyWay:mainfrom
mohammed-io:feat/completion-reminder

Conversation

@mohammed-io

@mohammed-io mohammed-io commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Context

After discussing on #162 we have decided to add the completions suggestion as the hint for the user shell.

I went with the simplest solution. It meant to support the 3 major shells (bash, zsh, and fish) however, yargs doesn't support fish at the moment until yargs/yargs#2569 is merged and released. So, I added the support for fish anyway, but with a check to not show the completion on fish shell and a comment to remove the check after that PR is merged.

@jamie-at-bunny WDYT?

@bunnynet-devops

Copy link
Copy Markdown

@codex review

@changeset-bot

changeset-bot Bot commented Sep 1, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: b8275b3

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 6 packages
Name Type
@bunny.net/cli Patch
@bunny.net/cli-darwin-arm64 Patch
@bunny.net/cli-darwin-x64 Patch
@bunny.net/cli-linux-arm64 Patch
@bunny.net/cli-linux-x64 Patch
@bunny.net/cli-windows-x64 Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 1, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-09-01T12:16:09.360783Z 5b35f69 Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@mohammed-io
mohammed-io marked this pull request as draft September 1, 2026 11:52

@chatgpt-codex-connector chatgpt-codex-connector 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.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 0d603c704c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread packages/cli/src/commands/completion/hint.ts Outdated

// yargs doesn't support fish shell completions yet until next release.
// Once https://github.com/yargs/yargs/pull/2569 is merged, remove this check.
if (shell?.includes("fish")) return;

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Align the advertised Fish hint with the runtime guard

With $SHELL=/usr/bin/fish, this return guarantees that a successful login prints no completion line, while the updated README says login prints the exact line for the user's shell and the changeset explicitly advertises a Fish completions file. Fish users therefore never receive the announced onboarding behavior; remove the Fish claim until yargs supports it, or generate a valid Fish completion and allow the hint through. The README is this repository's command-behavior reference.

AGENTS.md reference: AGENTS.md:L3-L5

Useful? React with 👍 / 👎.

Comment thread packages/cli/src/commands/completion/hint.ts Outdated
Comment thread packages/cli/src/commands/completion/hint.ts Outdated
@mohammed-io
mohammed-io marked this pull request as ready for review September 1, 2026 12:13
@bunnynet-devops

Copy link
Copy Markdown

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Swish!

Reviewed commit: 5b35f691fc

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread .changeset/completion-login-hint.md Outdated
@mohammed-io

Copy link
Copy Markdown
Contributor Author

Saw the conflicts, fixing them.

@mohammed-io

mohammed-io commented Sep 3, 2026

Copy link
Copy Markdown
Contributor Author

Good to go @jamie-at-bunny .

Let me know what else I can help with, I have good free time these days. Or if you have a vision in mind or a roadmap, I can work from there and help you shape it into reality. I am not a bunny.net customer, I will have to subscribe to know more about what's going on inside (it has no free tier AFAIK, so I will try to work around it)

@jamie-at-bunny

Copy link
Copy Markdown
Member

@mohammed-io looks great! I'll get this merged today. If you signup, I can give you some credit and extend the trial as a thanks for your contributions 😄

One the next areas are to:

  1. Create a @bunny.net/tools package that contains the business logic from the commands themselves. Almost introducing a "service" layer. This package can then be shared with an MCP tool I'm working on.
  2. Improve apps developer experience
  3. Improve overall developer experience - making sure commands are intuitive, and we ask the right questions/prompts at the right time to keep the flow going.
  4. Adding better examples/descriptions to commands.

@mohammed-io

Copy link
Copy Markdown
Contributor Author

@mohammed-io looks great! I'll get this merged today. If you signup, I can give you some credit and extend the trial as a thanks for your contributions 😄

Thank you! I will let you know about my account details when I sign up!

One the next areas are to:

  1. Create a @bunny.net/tools package that contains the business logic from the commands themselves. Almost introducing a "service" layer. This package can then be shared with an MCP tool I'm working on.

  2. Improve apps developer experience

  3. Improve overall developer experience - making sure commands are intuitive, and we ask the right questions/prompts at the right time to keep the flow going.

  4. Adding better examples/descriptions to commands.

For 1. Would need more context. Since you are working on the MCP I can see how it goes after that.

I will start with 4. it will give me a good taste on the DX of the cli and it gives me more context working on the others.

How do you work normally? Should I create a github issue before start working?

@jamie-at-bunny

Copy link
Copy Markdown
Member

@mohammed-io feel free to open an issue for Yargs based examples for the commands. I think most commands have some examples, but it would be good to audit those and add any missing ones.

Open an issue, and mention you'll work on it.

Since it's mostly myself and @amir-at-bunny contributing to the CLI right now, we just mostly use internal Slack to discuss our ideas and then spike a PR to take forward. But I won't be touching examples, so feel free to take that. Appreciate the contribution 🫶

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.

3 participants