Skip to content

feat(triage): add area/documentation to issue triage#21222

Merged
g-samroberts merged 1 commit intomainfrom
docs-triage-instructions
Mar 5, 2026
Merged

feat(triage): add area/documentation to issue triage#21222
g-samroberts merged 1 commit intomainfrom
docs-triage-instructions

Conversation

@g-samroberts
Copy link
Contributor

@g-samroberts g-samroberts commented Mar 5, 2026

Summary

Adds details on the 'area/documentation' label to the automated and scheduled issue triage workflows.

This ensures that issues related to documentation are correctly labeled, improving the organization of the issue tracker.

Fixes google-gemini/maintainers-gemini-cli#1483

Adds the 'area/documentation' label to the automated and scheduled issue triage workflows.

This ensures that issues related to documentation are correctly labeled, improving the organization of the issue tracker.
@g-samroberts g-samroberts requested a review from a team as a code owner March 5, 2026 05:57
@gemini-code-assist
Copy link
Contributor

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

@gemini-cli
Copy link
Contributor

gemini-cli bot commented Mar 5, 2026

Hi there! Thank you for your contribution to Gemini CLI.

To improve our contribution process and better track changes, we now require all pull requests to be associated with an existing issue, as announced in our recent discussion and as detailed in our CONTRIBUTING.md.

This pull request is being closed because it is not currently linked to an issue. Once you have updated the description of this PR to link an issue (e.g., by adding Fixes #123 or Related to #123), it will be automatically reopened.

How to link an issue:
Add a keyword followed by the issue number (e.g., Fixes #123) in the description of your pull request. For more details on supported keywords and how linking works, please refer to the GitHub Documentation on linking pull requests to issues.

Thank you for your understanding and for being a part of our community!

@gemini-cli
Copy link
Contributor

gemini-cli bot commented Mar 5, 2026

Hi @g-samroberts, thank you so much for your contribution to Gemini CLI! We really appreciate the time and effort you've put into this.

We're making some updates to our contribution process to improve how we track and review changes. Please take a moment to review our recent discussion post: Improving Our Contribution Process & Introducing New Guidelines.

Key Update: Starting January 26, 2026, the Gemini CLI project will require all pull requests to be associated with an existing issue. Any pull requests not linked to an issue by that date will be automatically closed.

Thank you for your understanding and for being a part of our community!

@gemini-cli gemini-cli bot closed this Mar 5, 2026
@g-samroberts g-samroberts reopened this Mar 5, 2026
@gemini-cli gemini-cli bot added the status/need-issue Pull requests that need to have an associated issue. label Mar 5, 2026
@github-actions
Copy link

github-actions bot commented Mar 5, 2026

Size Change: -2 B (0%)

Total Size: 26 MB

ℹ️ View Unchanged
Filename Size Change
./bundle/gemini.js 25.5 MB -2 B (0%)
./bundle/node_modules/@google/gemini-cli-devtools/dist/client/main.js 221 kB 0 B
./bundle/node_modules/@google/gemini-cli-devtools/dist/src/_client-assets.js 227 kB 0 B
./bundle/node_modules/@google/gemini-cli-devtools/dist/src/index.js 11.5 kB 0 B
./bundle/node_modules/@google/gemini-cli-devtools/dist/src/types.js 132 B 0 B
./bundle/sandbox-macos-permissive-open.sb 890 B 0 B
./bundle/sandbox-macos-permissive-proxied.sb 1.31 kB 0 B
./bundle/sandbox-macos-restrictive-open.sb 3.36 kB 0 B
./bundle/sandbox-macos-restrictive-proxied.sb 3.56 kB 0 B
./bundle/sandbox-macos-strict-open.sb 4.82 kB 0 B
./bundle/sandbox-macos-strict-proxied.sb 5.02 kB 0 B

compressed-size-action

@g-samroberts g-samroberts added this pull request to the merge queue Mar 5, 2026
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to no response for status checks Mar 5, 2026
@g-samroberts g-samroberts added this pull request to the merge queue Mar 5, 2026
Merged via the queue into main with commit 93d9adc Mar 5, 2026
37 of 55 checks passed
@g-samroberts g-samroberts deleted the docs-triage-instructions branch March 5, 2026 18:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

status/need-issue Pull requests that need to have an associated issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants