mirror of
https://github.com/google-gemini/gemini-cli.git
synced 2026-05-13 05:12:55 -07:00
docs: add missing .md extensions to internal doc links (#24145)
This commit is contained in:
@@ -398,8 +398,8 @@ on this page.
|
|||||||
|
|
||||||
## Running in headless mode <a id="headless"></a>
|
## Running in headless mode <a id="headless"></a>
|
||||||
|
|
||||||
[Headless mode](../cli/headless) will use your existing authentication method,
|
[Headless mode](../cli/headless.md) will use your existing authentication
|
||||||
if an existing authentication credential is cached.
|
method, if an existing authentication credential is cached.
|
||||||
|
|
||||||
If you have not already signed in with an authentication credential, you must
|
If you have not already signed in with an authentication credential, you must
|
||||||
configure authentication using environment variables:
|
configure authentication using environment variables:
|
||||||
|
|||||||
+6
-6
@@ -22,11 +22,11 @@ With hooks, you can:
|
|||||||
|
|
||||||
### Getting started
|
### Getting started
|
||||||
|
|
||||||
- **[Writing hooks guide](../hooks/writing-hooks)**: A tutorial on creating your
|
- **[Writing hooks guide](../hooks/writing-hooks.md)**: A tutorial on creating
|
||||||
first hook with comprehensive examples.
|
your first hook with comprehensive examples.
|
||||||
- **[Best practices](../hooks/best-practices)**: Guidelines on security,
|
- **[Best practices](../hooks/best-practices.md)**: Guidelines on security,
|
||||||
performance, and debugging.
|
performance, and debugging.
|
||||||
- **[Hooks reference](../hooks/reference)**: The definitive technical
|
- **[Hooks reference](../hooks/reference.md)**: The definitive technical
|
||||||
specification of I/O schemas and exit codes.
|
specification of I/O schemas and exit codes.
|
||||||
|
|
||||||
## Core concepts
|
## Core concepts
|
||||||
@@ -154,8 +154,8 @@ Gemini CLI **fingerprints** project hooks. If a hook's name or command changes
|
|||||||
(e.g., via `git pull`), it is treated as a **new, untrusted hook** and you will
|
(e.g., via `git pull`), it is treated as a **new, untrusted hook** and you will
|
||||||
be warned before it executes.
|
be warned before it executes.
|
||||||
|
|
||||||
See [Security Considerations](../hooks/best-practices#using-hooks-securely) for
|
See [Security Considerations](../hooks/best-practices.md#using-hooks-securely)
|
||||||
a detailed threat model.
|
for a detailed threat model.
|
||||||
|
|
||||||
## Managing hooks
|
## Managing hooks
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user