### Backlog Health & Stale Policy Optimization#26304
Draft
gemini-cli-robot wants to merge 1 commit intomainfrom
Draft
### Backlog Health & Stale Policy Optimization#26304gemini-cli-robot wants to merge 1 commit intomainfrom
gemini-cli-robot wants to merge 1 commit intomainfrom
Conversation
#### Problem Statement Current repository metrics (`latency`, `throughput`) suffer from **survivorship bias**: they only sample the last 100 *closed* items, making the repository appear healthier than it is. Meanwhile, a stable backlog of **2342 open issues** and **442 open PRs** persists, largely due to "staleness immunity" for `help wanted` items and throttling in the standard stale workflow. #### Changes 1. **New Metric: Backlog Age**: Added `tools/gemini-cli-bot/metrics/scripts/backlog_age.ts` to measure the median age of the oldest 100 open issues and PRs. This exposes the "Slow Path" bottleneck that was previously invisible. 2. **Stale Policy Throttling Fix**: Increased `operations-per-run` from 30 (default) to 200 in `.github/workflows/stale.yml` to allow the daily cron to actually make progress on the large backlog. 3. **Help-Wanted Expiration**: Updated `gemini-scheduled-stale-issue-closer.yml` to remove the infinite exemption for `help wanted` issues. They are now eligible for stale closure if they are older than 180 days and have no recent human activity. #### Expected Impact - **Visibility**: The new `backlog_age` metrics will likely show high values initially, providing a baseline for backlog reduction efforts. - **Efficiency**: Throttling fix will increase the rate of stale item closure. - **Backlog Reduction**: The 6-month expiration for `help wanted` will finally address legacy "immortal" issues that have been bloating the backlog for years. This is a surgical PR focused on repository health and metric accuracy.
|
Size Change: -4 B (0%) Total Size: 33.9 MB
ℹ️ View Unchanged
|
Draft
18 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backlog Health & Stale Policy Optimization
Problem Statement
Current repository metrics (
latency,throughput) suffer from survivorship bias: they only sample the last 100 closed items, making the repository appear healthier than it is. Meanwhile, a stable backlog of 2342 open issues and 442 open PRs persists, largely due to "staleness immunity" forhelp wanteditems and throttling in the standard stale workflow.Changes
tools/gemini-cli-bot/metrics/scripts/backlog_age.tsto measure the median age of the oldest 100 open issues and PRs. This exposes the "Slow Path" bottleneck that was previously invisible.operations-per-runfrom 30 (default) to 200 in.github/workflows/stale.ymlto allow the daily cron to actually make progress on the large backlog.gemini-scheduled-stale-issue-closer.ymlto remove the infinite exemption forhelp wantedissues. They are now eligible for stale closure if they are older than 180 days and have no recent human activity.Expected Impact
backlog_agemetrics will likely show high values initially, providing a baseline for backlog reduction efforts.help wantedwill finally address legacy "immortal" issues that have been bloating the backlog for years.This is a surgical PR focused on repository health and metric accuracy.