Skip to content

docs: make env vars copy/paste-able #42

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
duwenxin99 merged 4 commits into from
Oct 17, 2025
Merged

docs: make env vars copy/paste-able #42

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
15656b5
docs: update readme with form
averikitsch Oct 14, 2025
2f7869f
docs: make env vars copy/paste-able
averikitsch Oct 16, 2025
a6e68fd
Merge branch 'main' into env-var-updates
averikitsch Oct 16, 2025
5616573
Merge branch 'main' into env-var-updates
duwenxin99 Oct 17, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 5 additions & 6 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,9 +19,6 @@ Learn more about [Gemini CLI Extensions](https://github.com/google-gemini/gemini
* **Seamless Workflow:** Stay in your CLI. No need to constantly switch contexts to the GCP console for generating analytics insights. .
* **Leverage prebuilt agent :** Access to advanced insights offered by a built-in agent behind [Conversational Analytics API](https://cloud.google.com/gemini/docs/conversational-analytics-api/overview)




## Prerequisites

Before you begin, ensure you have the following:
Expand All @@ -48,9 +45,11 @@ gemini extensions install https://github.com/gemini-cli-extensions/bigquery-conv

Set the following environment variables before starting the Gemini CLI. These variables can be loaded from a `.env` file.

* `BIGQUERY_PROJECT`: The GCP project ID.
* `BIGQUERY_LOCATION`: (Optional) The dataset location.
* `BIGQUERY_USE_CLIENT_OAUTH`: (Optional) Set to `true` to use client-side OAuth for authorization.
```bash
export BIGQUERY_PROJECT="<your-gcp-project-id>"
export BIGQUERY_LOCATION="<your-dataset-location>" # Optional
export BIGQUERY_USE_CLIENT_OAUTH="true" # Optional
```

Ensure [Application Default Credentials](https://cloud.google.com/docs/authentication/gcloud) are available in your environment.

Expand Down
Loading