Add issue for automated changelogs

[g-samroberts]

Summary

Add issue for automated changelogs, so they show up on our project board. Currently automatically generated changelog PRs don't have an issue tied to them, and can get lost in the PR mix.

With this change, changelogs will link to #18505. This way the auto triage both will transitively apply the area/documentation label and put the PR in Technical Writer project, so it appears on our PR review list. This is the main changelog issue, this also serves to put all changelog PRs under one issue for easier search/development.

Note that this is different from the issue that engineering might use to track the release that results in the changelog.

Related to #18505

[gemini-cli]

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]

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-code-assist]

Note

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

[github-actions]

Size Change: -4 B (0%)

Total Size: 26.2 MB

ℹ️ View Unchanged

Filename	Size	Change
./bundle/gemini.js	25.7 MB	-4 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}

[jerop]

also if a changelog PR is opened after a patch, it'll be useful to link the PR to the patched PR so that maintainers remember to review and merge it - something like this: #21713 (comment)

[g-samroberts]

@jerop That would be helpful in tracking + merging the changelog update, but this workflow is triggered by the release event as opposed to a dispatch like the workflow that creates the patch comments. I'm not sure the patch PR would be available to this workflow... any ideas? This could be a good area for future improvement.

For now my aim was to tie it to the Docs tracking issue so it transitively gets the TW project applied, which means it shows up on our PR tracking list.

Let me know your thoughts!