Answer: The workflow automatically unassigns external contributors who have not opened a linked pull request within 7 days of being assigned, while maintainers, org members, and repo collaborators with write access or above are exempt. It runs every day at 09:00 UTC and can also be triggered manually with an optional dry_run mode. Status: Confirmed Entry: tool/gemini-cli/agents-and-automation/unassign-inactive-assignees Revision: 1 Digest: sha256:a192ea3f0b838266 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:18:42Z Last changed: 2026-11-13T03:18:42Z Last verified: 2026-11-20T12:53:19Z Next check: 2026-11-21T12:53:19Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Unit | Source | As of Inactivity threshold | 7 days | days | [1] | 2026-11-20 Schedule | Every day at 09:00 UTC | | [1] | 2026-11-20 Workflow file | .github/workflows/unassign-inactive-assignees.yml | | [1] | 2026-11-20 Unassignment threshold | more than 7 days | days | [1] | 2026-11-20 Exempt users | Maintainers, org members, and repo collaborators with write access or above | | [1] | 2026-11-20 Manual trigger option | dry_run | | [1] | 2026-11-20 Sources: [1] Google. "Automation and triage processes". https://geminicli.com/docs/issue-and-pr-automation.md Role: primary. Accessed: 2026-11-20T12:53:19Z Quote: "opened a linked pull request within **7 days** of being assigned" (Supports: Inactivity threshold) Quote: "Every day at 09:00 UTC, and can be triggered manually with" (Supports: Schedule) Quote: "`.github/workflows/unassign-inactive-assignees.yml`" (Supports: Workflow file) Quote: "If an assignee has been assigned for **more than 7 days** and no qualifying" (Supports: Unassignment threshold) Quote: "Maintainers, org members, and repo collaborators with write access or above are always exempt" (Supports: Exempt users) Quote: "an optional `dry_run` mode" (Supports: Manual trigger option) Published: 2026-10-16T02:36:07Z Snapshot SHA-256: 2e12674f60c3cae97ae1bc68c9e2c522de3453c71321ee8be4880811bacce112 (captured 2026-11-13T03:18:41Z) 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:42Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:53:19Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:53:19Z Last attempt: 2026-11-20T12:53:19Z Notes and limitations: Extracted automatically from a single official source (section "5. Automatic unassignment of inactive contributors: `Unassign Inactive Issue Assignees`"). Related: https://latestn.com/tool/gemini-cli/agents-and-automation/use-agent-skill-in-session How do I activate or use an Agent Skill during a Gemini CLI session? https://latestn.com/tool/gemini-cli/agents-and-automation/write-skill-description How do I write a good description for a Gemini CLI Agent Skill? https://latestn.com/tool/gemini-cli/commands-and-shortcuts/add-custom-command How do I add a custom command to a Gemini CLI extension? https://latestn.com/tool/gemini-cli/agents-and-automation/tool-hook-matchers How do I use a matcher to filter which tools a Gemini CLI hook runs for? https://latestn.com/tool/gemini-cli/agents-and-automation/trigger-headless-mode How do I trigger headless mode in Gemini CLI? https://latestn.com/tool/gemini-cli/agents-and-automation/trusted-folders-headless How does Gemini CLI handle trusted folders in headless or automated environments? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:18:42Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/gemini-cli/agents-and-automation/unassign-inactive-assignees/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/agents-and-automation/unassign-inactive-assignees POST: https://latestn.com/dispute/tool/gemini-cli/agents-and-automation/unassign-inactive-assignees with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/gemini-cli/agents-and-automation/unassign-inactive-assignees?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How does Gemini CLI automatically unassign inactive issue assignees? Revision 1, last verified 2026-11-20T12:53:19Z. https://latestn.com/tool/gemini-cli/agents-and-automation/unassign-inactive-assignees (accessed 2026-11-21T10:07:41Z). @misc{LatestN_tool_gemini_cli_agents_and_automation_unassign_inactive_assignees_r1, title = {How does Gemini CLI automatically unassign inactive issue assignees?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/gemini-cli/agents-and-automation/unassign-inactive-assignees}}, note = {Revision 1; digest sha256:a192ea3f0b838266; last verified 2026-11-20T12:53:19Z; accessed 2026-11-21T10:07:41Z} } 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/agents-and-automation/unassign-inactive-assignees