Skip to content

Rename Gemini CLI to Antigravity CLI in MCP client mentions - #401

Open
arpadkun wants to merge 2 commits into
mainfrom
claude/live-content-changes-04572e
Open

arpadkun wants to merge 2 commits into
mainfrom
claude/live-content-changes-04572e

Conversation

@arpadkun

Copy link
Copy Markdown
Contributor

Summary

Google replaced Gemini CLI with Antigravity CLI (agy). This updates every prose mention of "Gemini CLI" as a supported Bitrise MCP client on the pages we maintain by hand:

  • docs/bitrise-platform/ai/bitrise-mcp/bitrise-mcp.mdx: supported clients list
  • docs/bitrise-platform/ai/ai-features-on-bitrise.mdx: client list
  • docs/bitrise-platform/ai/onboarding-for-agents.mdx: link text and the restart note
  • static/onboarding-for-agents.md: the static copy of the onboarding page
  • Matching i18n/ja/ copies of the three pages

Not in this PR

  • Install guide (install-gemini-cli.mdx): this page is synced from bitrise-io/bitrise-mcp/docs, and its steps (gemini extensions install, ~/.gemini/settings.json, url) don't carry over to agy. A rewritten guide, a new slug and a redirect will follow separately. Until then, the onboarding page's "Google Antigravity CLI" link still opens the existing guide.
  • Changelog entry: it records what shipped at the time, so it keeps the old name.
  • AI FAQ "Gemini models" row: it's about the models, not the CLI.

Checks

  • node scripts/check-links-source.js passes on the three English pages.
  • All edited pages already have a description in their frontmatter.
  • No slugs changed, so no redirects are needed.

🤖 Generated with Claude Code

Google replaced Gemini CLI with Antigravity CLI. Update the client
lists on the hand-maintained AI pages, their Japanese copies, and the
static onboarding-for-agents mirror.

The synced install guide (install-gemini-cli) is unchanged: its steps
are Gemini CLI specific and the source lives in bitrise-io/bitrise-mcp.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

The English page was restructured in 2a7170f (Step and CLI
subsections), but the JA copy kept the old layout, so ja-structure
failed on any PR touching i18n/ja: 13 vs 3 code blocks, 10 vs 14
links, 3 vs 5 headings. Retranslated the whole page with
scripts/ja_manual_translate.py; ja_structure.py and the JTF
textlint check both pass.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
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.

1 participant