@@ -17,37 +17,22 @@ Before you begin, ensure you have the following:
1717
1818### Running from Local Source
1919
20- The core logic for this extension is handled by a pre-built ` toolbox ` binary. The development process involves installing the extension locally into the Gemini CLI to test changes.
21-
22201 . ** Clone the Repository:**
2321
2422 ``` bash
2523 git clone https://github.com/gemini-cli-extensions/cloud-sql-postgresql.git
2624 cd cloud-sql-postgresql
2725 ```
2826
29- 2. ** Download the Toolbox Binary:** The required version of the ` toolbox` binary
30- is specified in ` toolbox_version.txt` . Download it for your platform.
31-
32- ` ` ` bash
33- # Read the required version
34- VERSION=$( cat toolbox_version.txt)
35-
36- # Example for macOS/amd64
37- curl -L -o toolbox https://storage.googleapis.com/mcp-toolbox-for-databases/geminicli/v$VERSION /darwin/amd64/toolbox
38- chmod +x toolbox
39- ` ` `
40- Adjust the URL for your operating system (` linux/amd64` , ` darwin/arm64` , ` windows/amd64` ).
41-
42- 3. ** Install the Extension Locally:** Use the Gemini CLI to install the
27+ 2. ** Install the Extension Locally:** Use the Gemini CLI to install the
4328 extension from your local directory.
4429
4530 ` ` ` bash
4631 gemini extensions install .
4732 ` ` `
4833 The CLI will prompt you to confirm the installation. Accept it to proceed.
4934
50- 4 . ** Testing Changes:** After installation, start the Gemini CLI (` gemini` ).
35+ 3 . ** Testing Changes:** After installation, start the Gemini CLI (` gemini` ).
5136 You can now interact with the ` cloud-sql-postgresql` tools to manually test your changes
5237 against your connected database.
5338
@@ -59,9 +44,9 @@ A GitHub Actions workflow (`.github/workflows/presubmit-tests.yml`) is triggered
5944for every pull request. This workflow primarily verifies that the extension can
6045be successfully installed by the Gemini CLI.
6146
62- Currently, there are no automated unit or integration test suites
63- within this repository. All functional testing must be performed manually. All tools
64- are currently tested in the [MCP Toolbox GitHub](https://github.com/googleapis/mcp-toolbox) .
47+ All tools are currently tested in the [MCP Toolbox GitHub](https://github.com/googleapis/mcp-toolbox).
48+
49+ The skills themselves are validated using the ` skills-validate.yml ` workflow .
6550
6651# ## Other GitHub Checks
6752
@@ -74,17 +59,6 @@ are currently tested in the [MCP Toolbox GitHub](https://github.com/googleapis/m
7459* ** Dependency Updates:** [Renovate](https://github.com/apps/forking-renovate)
7560 is configured to automatically create pull requests for dependency updates.
7661
77- # # Building the Extension
78-
79- The " build" process for this extension involves packaging the extension' s
80- metadata files (`gemini-extension.json`, `cloud-sql-postgresql.md`, `LICENSE`) along with the
81- pre-built `toolbox` binary into platform-specific archives (`.tar.gz` or `.zip`).
82-
83- This process is handled automatically by the
84- [`package-and-upload-assets.yml`](.github/workflows/package-and-upload-assets.yml)
85- GitHub Actions workflow when a new release is created. Manual building is not
86- required.
87-
8862# # Maintainer Information
8963
9064# ## Team
@@ -139,7 +113,3 @@ The process is handled by the [`mirror-changelog.yml`](.github/workflows/mirror-
1391132. **Merge Release PR:** A maintainer approves and merges the Release PR. This
140114 action triggers `release-please` to create a new GitHub tag and a
141115 corresponding GitHub Release.
142- 3. ** Package and Upload:** The new release triggers the
143- ` package-and-upload-assets.yml` workflow. This workflow builds the
144- platform-specific extension archives and uploads them as assets to the
145- GitHub Release.
0 commit comments