Answer: The pull request guidelines require linking all PRs to an existing issue, keeping PRs small and focused, using draft PRs for work in progress, ensuring all checks pass via `npm run preflight`, updating documentation for user-facing changes, and writing clear commit messages and PR descriptions following the Conventional Commits standard. Status: Confirmed Entry: tool/gemini-cli/features/pr-guidelines Revision: 1 Digest: sha256:367b9ccf8c063a66 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:18:10Z Last changed: 2026-11-13T03:18:10Z Last verified: 2026-11-20T12:52:18Z Next check: 2026-11-21T12:52:18Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Issue linking requirement | All PRs should be linked to an existing issue in our tracker. | [1] | 2026-11-20 PR scope guidance | We favor small, atomic PRs that address a single issue or add a single, self-contained feature. | [1] | 2026-11-20 Draft PR guidance | use GitHub's **Draft Pull Request** feature | [1] | 2026-11-20 Checks command | npm run preflight | [1] | 2026-11-20 Documentation directory | /docs | [1] | 2026-11-20 Commit message standard | Conventional Commits | [1] | 2026-11-20 Good PR title example | feat(cli): Add --json flag to 'config get' command | [1] | 2026-11-20 Sources: [1] Google. "How to contribute". https://geminicli.com/docs/contributing.md Role: primary. Accessed: 2026-11-20T12:52:18Z Quote: "All PRs should be linked to an existing issue in our tracker." (Supports: Issue linking requirement) Quote: "We favor small, atomic PRs that address a single issue or add a single, self-contained feature." (Supports: PR scope guidance) Quote: "please use GitHub's **Draft Pull Request** feature" (Supports: Draft PR guidance) Quote: "running `npm run preflight`" (Supports: Checks command) Quote: "update the relevant documentation in the `/docs` directory" (Supports: Documentation directory) Quote: "Follow the [Conventional Commits](https://www.conventionalcommits.org/) standard for your commit messages." (Supports: Commit message standard) Quote: "**Good PR title:** `feat(cli): Add --json flag to 'config get' command`" (Supports: Good PR title example) Published: 2026-10-16T02:36:07Z Snapshot SHA-256: 6d9bc6fd35815e3c9a15d0c342c60483ae66da10a70b4a36a2be2d2a2233b60b (captured 2026-11-13T03:18:09Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:18:10Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:52:18Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:52:18Z Last attempt: 2026-11-20T12:52:18Z Notes and limitations: Extracted automatically from a single official source (section "Pull request guidelines"). Related: https://latestn.com/tool/gemini-cli/features/read-file-tool How do I read a specific file with Gemini CLI's read_file tool? https://latestn.com/tool/gemini-cli/features/release-cadence-and-tags What are the release cadence and tags for Gemini CLI? https://latestn.com/tool/gemini-cli/features/release-types What release types does Gemini CLI have? https://latestn.com/tool/gemini-cli/features/list-themes What themes are available in Gemini CLI? https://latestn.com/tool/gemini-cli/features/manage-background-processes How does Gemini CLI handle background processes and active shells? https://latestn.com/tool/gemini-cli/features/notification-types What types of notifications does Gemini CLI send? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:18:10Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/gemini-cli/features/pr-guidelines/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/gemini-cli/features/pr-guidelines POST: https://latestn.com/dispute/tool/gemini-cli/features/pr-guidelines with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/gemini-cli/features/pr-guidelines?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What are the pull request guidelines for contributing to Gemini CLI? Revision 1, last verified 2026-11-20T12:52:18Z. https://latestn.com/tool/gemini-cli/features/pr-guidelines (accessed 2026-11-21T09:52:48Z). @misc{LatestN_tool_gemini_cli_features_pr_guidelines_r1, title = {What are the pull request guidelines for contributing to Gemini CLI?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/gemini-cli/features/pr-guidelines}}, note = {Revision 1; digest sha256:367b9ccf8c063a66; last verified 2026-11-20T12:52:18Z; accessed 2026-11-21T09:52:48Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/gemini-cli/features/pr-guidelines