summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJaana Dogan <[email protected]>2025-04-17 14:39:13 -0700
committerGitHub <[email protected]>2025-04-17 14:39:13 -0700
commitd3ee91ff9203f8591ca7a7101ce9ccadeb8137be (patch)
tree4516df1e675d7d4d78202bd132b8af03e94ebcb3
parentd970882428a264d122b2f60fc91a4d72da912a93 (diff)
parenta280727248758a6d5c26c65d06af10efa12eef26 (diff)
Merge pull request #3 from google-gemini/readme
Remove internal docs and mention of Gerrit from README
-rw-r--r--README.md10
1 files changed, 0 insertions, 10 deletions
diff --git a/README.md b/README.md
index 063cc60f..9644e8cb 100644
--- a/README.md
+++ b/README.md
@@ -4,10 +4,6 @@
This repository contains the Gemini Code CLI tool.
-## Cloning and Contribution
-
-This project uses Gerrit for version control. For details on the development workflow, including how to clone the repository and contribute changes, please refer to the [Gerrit Dev Workflows](http://go/gerrit-dev-workflows).
-
## Setup
1. **Get a Gemini API Key:** Obtain your API key from Google AI Studio: [https://aistudio.google.com/app/apikey](https://aistudio.google.com/app/apikey)
@@ -55,9 +51,3 @@ To debug the CLI application using VS Code:
2. In VS Code, use the "Attach" launch configuration (found in `.vscode/launch.json`). This configuration is set up to attach to the Node.js process listening on port 9229, which is the default port used by `--inspect-brk`.
Alternatively, you can use the "Launch Program" configuration in VS Code if you prefer to launch the currently open file directly, but the "Attach" method is generally recommended for debugging the main CLI entry point.
-
-## Related
-
-- [Document](http://go/gemini-code-cli)
-- [Video Walkthrough](https://screencast.googleplex.com/cast/NDkwMjUwMzMxMjI2MTEyMHwwOWZkMjQzYy03Mw)
-