mirror of
https://github.com/google-gemini/gemini-cli.git
synced 2026-05-14 05:42:54 -07:00
fix(bot): satisfy YAML lint rules and clarify monorepo build order
This commit is contained in:
@@ -32,10 +32,10 @@ on:
|
||||
description: 'Mandate to execute'
|
||||
type: 'choice'
|
||||
options:
|
||||
- auto
|
||||
- issue-fixer
|
||||
- metrics
|
||||
- interactive
|
||||
- 'auto'
|
||||
- 'issue-fixer'
|
||||
- 'metrics'
|
||||
- 'interactive'
|
||||
default: auto
|
||||
|
||||
concurrency:
|
||||
|
||||
@@ -83,6 +83,10 @@ For any detected bugs, bottlenecks, or opportunities:
|
||||
- **Delegation Guidelines**: Do NOT delegate to the 'generalist' agent. Delegate
|
||||
data-intensive tasks (like repository metrics collection) to the 'worker'
|
||||
agent.
|
||||
- **Monorepo Build Order**: When verifying the workspace or diagnosing errors,
|
||||
you MUST run `npm run build` BEFORE running `npm run typecheck`. In a clean
|
||||
state, `tsc` will report widespread errors (TS6305) if the project's build
|
||||
artifacts do not yet exist. These are environment issues, not code bugs.
|
||||
- **Strict Read-Only Reasoning**: You cannot push code or post comments via API.
|
||||
Your only way to effect change is by writing to specific files and explicitly
|
||||
staging file changes using the `git add` command.
|
||||
|
||||
Reference in New Issue
Block a user