Skip to content

πŸ” Auto-rebase Health β€” Daily ReportΒ #767

Open

Description

@github-actions

Tracking issue for the daily Auto-rebase Health report. Each run posts a new comment below with the agentic-conflict-resolution rate and the auto-rebase fan-out CI-volume estimate.

Source: scripts/auto_rebase_health.sh Β· .github/workflows/auto-rebase-health.yml

Activity

  1. github-actions commented on Jun 16, 2026

    @github-actions
    ContributorAuthor

    πŸ” Auto-rebase Health β€” 2026-06-16

    Repo petry-projects/.github-private Β· lookback 7 day(s)

    Agentic conflict-resolution rate

    • Sentinels fired (<!-- auto-rebase-conflict:): 86
    • Dev-lead rebase responses (intent=rebase): 58
    • Resolved & pushed (status=applied): 0
    • Resolution rate (responses Γ· sentinels): 67%
    • Applied rate (applied Γ· sentinels): 0%

    Auto-rebase fan-out volume (estimate)

    • Workflow runs (auto-rebase.yml): 84 total Β· 82 success Β· 0 failed
    • Behind-PR multiplier (open non-Dependabot PRs): 8
    • Estimated branch-update CI re-runs: ~672
    • Per-day baseline: 12.0 auto-rebase run(s)/day Β· ~96.0 CI re-run(s)/day

    Fan-out is an estimate β€” per-run behind-PR counts are not logged in this repo, so re-runs = runs Γ— current open non-Dependabot PR count.

  2. github-actions commented on Jun 17, 2026

    @github-actions
    ContributorAuthor

    πŸ” Auto-rebase Health β€” 2026-06-17

    Repo petry-projects/.github-private Β· lookback 7 day(s)

    Agentic conflict-resolution rate

    • Sentinels fired (<!-- auto-rebase-conflict:): 71
    • Dev-lead rebase responses (intent=rebase): 52
    • Resolved & pushed (status=applied): 0
    • Resolution rate (responses Γ· sentinels): 73%
    • Applied rate (applied Γ· sentinels): 0%

    Auto-rebase fan-out volume (estimate)

    • Workflow runs (auto-rebase.yml): 65 total Β· 64 success Β· 0 failed
    • Behind-PR multiplier (open non-Dependabot PRs): 6
    • Estimated branch-update CI re-runs: ~390
    • Per-day baseline: 9.3 auto-rebase run(s)/day Β· ~55.7 CI re-run(s)/day

    Fan-out is an estimate β€” per-run behind-PR counts are not logged in this repo, so re-runs = runs Γ— current open non-Dependabot PR count.

  3. github-actions commented on Jun 18, 2026

    @github-actions
    ContributorAuthor

    πŸ” Auto-rebase Health β€” 2026-06-18

    Repo petry-projects/.github-private Β· lookback 7 day(s)

    Agentic conflict-resolution rate

    • Sentinels fired (<!-- auto-rebase-conflict:): 71
    • Dev-lead rebase responses (intent=rebase): 53
    • Resolved & pushed (status=applied): 0
    • Resolution rate (responses Γ· sentinels): 74%
    • Applied rate (applied Γ· sentinels): 0%

    Auto-rebase fan-out volume (estimate)

    • Workflow runs (auto-rebase.yml): 66 total Β· 65 success Β· 0 failed
    • Behind-PR multiplier (open non-Dependabot PRs): 3
    • Estimated branch-update CI re-runs: ~198
    • Per-day baseline: 9.4 auto-rebase run(s)/day Β· ~28.3 CI re-run(s)/day

    Fan-out is an estimate β€” per-run behind-PR counts are not logged in this repo, so re-runs = runs Γ— current open non-Dependabot PR count.

  4. github-actions commented on Jun 19, 2026

    @github-actions
    ContributorAuthor

    πŸ” Auto-rebase Health β€” 2026-06-19

    Repo petry-projects/.github-private Β· lookback 7 day(s)

    Agentic conflict-resolution rate

    • Sentinels fired (<!-- auto-rebase-conflict:): 50
    • Dev-lead rebase responses (intent=rebase): 36
    • Resolved & pushed (status=applied): 0
    • Resolution rate (responses Γ· sentinels): 72%
    • Applied rate (applied Γ· sentinels): 0%

    Auto-rebase fan-out volume (estimate)

    • Workflow runs (auto-rebase.yml): 62 total Β· 61 success Β· 0 failed
    • Behind-PR multiplier (open non-Dependabot PRs): 4
    • Estimated branch-update CI re-runs: ~248
    • Per-day baseline: 8.9 auto-rebase run(s)/day Β· ~35.4 CI re-run(s)/day

    Fan-out is an estimate β€” per-run behind-PR counts are not logged in this repo, so re-runs = runs Γ— current open non-Dependabot PR count.

  5. don-petry commented on Jun 20, 2026

    @don-petry
    Collaborator

    ⚠️ Root cause of the persistent 0% "applied" rate β€” it's a bug + a measurement artifact, not a clean signal

    The Applied rate (applied Γ· sentinels): 0% line in every report above is not evidence that agentic conflict-resolution never succeeds. Investigation (discussion #735) found two distinct problems, now fixed in #812:

    1. Conflict-file detection was broken. scripts/dev-lead-fix-reviews.sh parsed git merge-tree's changed in both header with awk '{print $NF}', yielding the literal word both instead of the conflicting filenames. The rebase prompt then restricted the engine to that nonexistent file, so resolutions aborted.
    2. applied was structurally unreachable. The rebase prompt has the engine force-push the rebased branch itself, so on success commit_and_push sees nothing to push and posts no-changes. So even successful rebases were recorded as no-changes β†’ 0% applied by construction.

    Implication for the metric: treat the applied/resolution-rate figures in the reports dated 2026-06-16 β†’ today as unreliable. The sentinels and responses counts and the fan-out estimate are unaffected.

    For story #739: source the agentic-conflict-resolution rate from the post-#812 report window once it has accumulated, not from the pre-fix numbers above. Until then the "does the custom system's conflict resolution actually work" question is unmeasured, so the Merge Queue go/no-go shouldn't lean on it either way.

    cc epic #736 / #739.


    Generated by Claude Code

  6. github-actions commented on Jun 20, 2026

    @github-actions
    ContributorAuthor

    πŸ” Auto-rebase Health β€” 2026-06-20

    Repo petry-projects/.github-private Β· lookback 7 day(s)

    Agentic conflict-resolution rate

    • Sentinels fired (<!-- auto-rebase-conflict:): 52
    • Dev-lead rebase responses (intent=rebase): 37
    • Resolved & pushed (status=applied): 0
    • Resolution rate (responses Γ· sentinels): 71%
    • Applied rate (applied Γ· sentinels): 0%

    Auto-rebase fan-out volume (estimate)

    • Workflow runs (auto-rebase.yml): 77 total Β· 76 success Β· 0 failed
    • Behind-PR multiplier (open non-Dependabot PRs): 4
    • Estimated branch-update CI re-runs: ~308
    • Per-day baseline: 11.0 auto-rebase run(s)/day Β· ~44.0 CI re-run(s)/day

    Fan-out is an estimate β€” per-run behind-PR counts are not logged in this repo, so re-runs = runs Γ— current open non-Dependabot PR count.

  7. github-actions commented on Jun 21, 2026

    @github-actions
    ContributorAuthor

    πŸ” Auto-rebase Health β€” 2026-06-21

    Repo petry-projects/.github-private Β· lookback 7 day(s)

    Agentic conflict-resolution rate

    • Sentinels fired (<!-- auto-rebase-conflict:): 40
    • Dev-lead rebase responses (intent=rebase): 28
    • Resolved & pushed (status=applied): 1
    • Resolution rate (responses Γ· sentinels): 70%
    • Applied rate (applied Γ· sentinels): 2%

    Auto-rebase fan-out volume (estimate)

    • Workflow runs (auto-rebase.yml): 78 total Β· 77 success Β· 0 failed
    • Behind-PR multiplier (open non-Dependabot PRs): 6
    • Estimated branch-update CI re-runs: ~468
    • Per-day baseline: 11.1 auto-rebase run(s)/day Β· ~66.9 CI re-run(s)/day

    Fan-out is an estimate β€” per-run behind-PR counts are not logged in this repo, so re-runs = runs Γ— current open non-Dependabot PR count.

  8. github-actions commented on Jun 22, 2026

    @github-actions
    ContributorAuthor

    πŸ” Auto-rebase Health β€” 2026-06-22

    Repo petry-projects/.github-private Β· lookback 7 day(s)

    Agentic conflict-resolution rate

    • Sentinels fired (<!-- auto-rebase-conflict:): 20
    • Dev-lead rebase responses (intent=rebase): 8
    • Resolved & pushed (status=applied): 3
    • Resolution rate (responses Γ· sentinels): 40%
    • Applied rate (applied Γ· sentinels): 15%

    Auto-rebase fan-out volume (estimate)

    • Workflow runs (auto-rebase.yml): 62 total Β· 62 success Β· 0 failed
    • Behind-PR multiplier (open non-Dependabot PRs): 8
    • Estimated branch-update CI re-runs: ~496
    • Per-day baseline: 8.9 auto-rebase run(s)/day Β· ~70.9 CI re-run(s)/day

    Fan-out is an estimate β€” per-run behind-PR counts are not logged in this repo, so re-runs = runs Γ— current open non-Dependabot PR count.

  9. github-actions commented on Jun 23, 2026

    @github-actions
    ContributorAuthor

    πŸ” Auto-rebase Health β€” 2026-06-23

    Repo petry-projects/.github-private Β· lookback 7 day(s)

    Agentic conflict-resolution rate

    • Sentinels fired (<!-- auto-rebase-conflict:): 21
    • Dev-lead rebase responses (intent=rebase): 8
    • Resolved & pushed (status=applied): 3
    • Resolution rate (responses Γ· sentinels): 38%
    • Applied rate (applied Γ· sentinels): 14%

    Auto-rebase fan-out volume (estimate)

    • Workflow runs (auto-rebase.yml): 60 total Β· 60 success Β· 0 failed
    • Behind-PR multiplier (open non-Dependabot PRs): 8
    • Estimated branch-update CI re-runs: ~480
    • Per-day baseline: 8.6 auto-rebase run(s)/day Β· ~68.6 CI re-run(s)/day

    Fan-out is an estimate β€” per-run behind-PR counts are not logged in this repo, so re-runs = runs Γ— current open non-Dependabot PR count.

  10. github-actions commented on Jun 24, 2026

    @github-actions
    ContributorAuthor

    πŸ” Auto-rebase Health β€” 2026-06-24

    Repo petry-projects/.github-private Β· lookback 7 day(s)

    Agentic conflict-resolution rate

    • Sentinels fired (<!-- auto-rebase-conflict:): 24
    • Dev-lead rebase responses (intent=rebase): 11
    • Resolved & pushed (status=applied): 7
    • Resolution rate (responses Γ· sentinels): 45%
    • Applied rate (applied Γ· sentinels): 29%

    Auto-rebase fan-out volume (estimate)

    • Workflow runs (auto-rebase.yml): 64 total Β· 64 success Β· 0 failed
    • Behind-PR multiplier (open non-Dependabot PRs): 4
    • Estimated branch-update CI re-runs: ~256
    • Per-day baseline: 9.1 auto-rebase run(s)/day Β· ~36.6 CI re-run(s)/day

    Fan-out is an estimate β€” per-run behind-PR counts are not logged in this repo, so re-runs = runs Γ— current open non-Dependabot PR count.

  11. github-actions commented on Jun 25, 2026

    @github-actions
    ContributorAuthor

    πŸ” Auto-rebase Health β€” 2026-06-25

    Repo petry-projects/.github-private Β· lookback 7 day(s)

    Agentic conflict-resolution rate

    • Sentinels fired (<!-- auto-rebase-conflict:): 24
    • Dev-lead rebase responses (intent=rebase): 10
    • Resolved & pushed (status=applied): 9
    • Resolution rate (responses Γ· sentinels): 41%
    • Applied rate (applied Γ· sentinels): 37%

    Auto-rebase fan-out volume (estimate)

    • Workflow runs (auto-rebase.yml): 62 total Β· 62 success Β· 0 failed
    • Behind-PR multiplier (open non-Dependabot PRs): 3
    • Estimated branch-update CI re-runs: ~186
    • Per-day baseline: 8.9 auto-rebase run(s)/day Β· ~26.6 CI re-run(s)/day

    Fan-out is an estimate β€” per-run behind-PR counts are not logged in this repo, so re-runs = runs Γ— current open non-Dependabot PR count.

  12. 117 remaining items

  13. github-actions commented on Oct 8, 2026

    @github-actions
    ContributorAuthor

    πŸ” Auto-rebase Health β€” 2026-10-08

    Repo petry-projects/.github-private Β· lookback 7 day(s)

    Agentic conflict-resolution rate

    • Sentinels fired (<!-- auto-rebase-conflict:): 49
    • Dev-lead rebase responses (intent=rebase): 29
    • Resolved & pushed (status=applied): 9
    • Resolution rate (responses Γ· sentinels): 59%
    • Applied rate (applied Γ· sentinels): 18%

    Auto-rebase fan-out volume (estimate)

    • Workflow runs (auto-rebase.yml): 27 total Β· 26 success Β· 0 failed
    • Behind-PR multiplier (open non-Dependabot PRs): 14
    • Estimated branch-update CI re-runs: ~378
    • Per-day baseline: 3.9 auto-rebase run(s)/day Β· ~54.0 CI re-run(s)/day

    Fan-out is an estimate β€” per-run behind-PR counts are not logged in this repo, so re-runs = runs Γ— current open non-Dependabot PR count.

    Fleet merge-state observability (AC7)

    • BEHIND (open non-draft non-Dependabot PRs mergeStateStatus: BEHIND): 0
    • DIRTY (open non-draft non-Dependabot PRs mergeStateStatus: DIRTY): 3

    Snapshot of the current open-PR queue, scoped to petry-projects/.github-private β€” fleet-wide counts would require a cross-repo PAT this report does not carry. Tracks the effectiveness of the AC1/AC2 auto-rebase fixes (combsmith/.github#926) without a manual audit.

    Base-merge necessity (#1881)

    • Up-to-date-branches policy (ruleset strict_required_status_checks_policy): false
    • Base merges required (behind actually blocks: strict on, enqueued in merge queue, or auto-rebase:ready label): 0
    • Base merges skippable (BEHIND with no such requirement β€” a no-op churn): 0
    • base_merges_required=0 base_merges_skippable=0

    Deterministic counter over open non-draft non-Dependabot BEHIND PRs (DIRTY PRs keep the conflict/rebase path, so they are excluded). skippable is the no-op base-merge volume #1881 removes at the source; it is the second input to #1864 AC #4 alongside #1865 reviews_carried_forward. The policy flag is read from repository configuration β€” if strict is re-armed, every BEHIND PR becomes required with no code change.

  14. github-actions commented on Oct 9, 2026

    @github-actions
    ContributorAuthor

    πŸ” Auto-rebase Health β€” 2026-10-09

    Repo petry-projects/.github-private Β· lookback 7 day(s)

    Agentic conflict-resolution rate

    • Sentinels fired (<!-- auto-rebase-conflict:): 75
    • Dev-lead rebase responses (intent=rebase): 32
    • Resolved & pushed (status=applied): 9
    • Resolution rate (responses Γ· sentinels): 42%
    • Applied rate (applied Γ· sentinels): 12%

    Auto-rebase fan-out volume (estimate)

    • Workflow runs (auto-rebase.yml): 30 total Β· 29 success Β· 0 failed
    • Behind-PR multiplier (open non-Dependabot PRs): 10
    • Estimated branch-update CI re-runs: ~300
    • Per-day baseline: 4.3 auto-rebase run(s)/day Β· ~42.9 CI re-run(s)/day

    Fan-out is an estimate β€” per-run behind-PR counts are not logged in this repo, so re-runs = runs Γ— current open non-Dependabot PR count.

    Fleet merge-state observability (AC7)

    • BEHIND (open non-draft non-Dependabot PRs mergeStateStatus: BEHIND): 0
    • DIRTY (open non-draft non-Dependabot PRs mergeStateStatus: DIRTY): 1

    Snapshot of the current open-PR queue, scoped to petry-projects/.github-private β€” fleet-wide counts would require a cross-repo PAT this report does not carry. Tracks the effectiveness of the AC1/AC2 auto-rebase fixes (combsmith/.github#926) without a manual audit.

    Base-merge necessity (#1881)

    • Up-to-date-branches policy (ruleset strict_required_status_checks_policy): false
    • Base merges required (behind actually blocks: strict on, enqueued in merge queue, or auto-rebase:ready label): 0
    • Base merges skippable (BEHIND with no such requirement β€” a no-op churn): 0
    • base_merges_required=0 base_merges_skippable=0

    Deterministic counter over open non-draft non-Dependabot BEHIND PRs (DIRTY PRs keep the conflict/rebase path, so they are excluded). skippable is the no-op base-merge volume #1881 removes at the source; it is the second input to #1864 AC #4 alongside #1865 reviews_carried_forward. The policy flag is read from repository configuration β€” if strict is re-armed, every BEHIND PR becomes required with no code change.

  15. github-actions commented on Oct 10, 2026

    @github-actions
    ContributorAuthor

    πŸ” Auto-rebase Health β€” 2026-10-10

    Repo petry-projects/.github-private Β· lookback 7 day(s)

    Agentic conflict-resolution rate

    • Sentinels fired (<!-- auto-rebase-conflict:): 77
    • Dev-lead rebase responses (intent=rebase): 28
    • Resolved & pushed (status=applied): 2
    • Resolution rate (responses Γ· sentinels): 36%
    • Applied rate (applied Γ· sentinels): 2%

    Auto-rebase fan-out volume (estimate)

    • Workflow runs (auto-rebase.yml): 35 total Β· 35 success Β· 0 failed
    • Behind-PR multiplier (open non-Dependabot PRs): 14
    • Estimated branch-update CI re-runs: ~490
    • Per-day baseline: 5.0 auto-rebase run(s)/day Β· ~70.0 CI re-run(s)/day

    Fan-out is an estimate β€” per-run behind-PR counts are not logged in this repo, so re-runs = runs Γ— current open non-Dependabot PR count.

    Fleet merge-state observability (AC7)

    • BEHIND (open non-draft non-Dependabot PRs mergeStateStatus: BEHIND): 0
    • DIRTY (open non-draft non-Dependabot PRs mergeStateStatus: DIRTY): 0

    Snapshot of the current open-PR queue, scoped to petry-projects/.github-private β€” fleet-wide counts would require a cross-repo PAT this report does not carry. Tracks the effectiveness of the AC1/AC2 auto-rebase fixes (combsmith/.github#926) without a manual audit.

    Base-merge necessity (#1881)

    • Up-to-date-branches policy (ruleset strict_required_status_checks_policy): false
    • Base merges required (behind actually blocks: strict on, enqueued in merge queue, or auto-rebase:ready label): 0
    • Base merges skippable (BEHIND with no such requirement β€” a no-op churn): 0
    • base_merges_required=0 base_merges_skippable=0

    Deterministic counter over open non-draft non-Dependabot BEHIND PRs (DIRTY PRs keep the conflict/rebase path, so they are excluded). skippable is the no-op base-merge volume #1881 removes at the source; it is the second input to #1864 AC #4 alongside #1865 reviews_carried_forward. The policy flag is read from repository configuration β€” if strict is re-armed, every BEHIND PR becomes required with no code change.

  16. github-actions commented on Oct 11, 2026

    @github-actions
    ContributorAuthor

    πŸ” Auto-rebase Health β€” 2026-10-11

    Repo petry-projects/.github-private Β· lookback 7 day(s)

    Agentic conflict-resolution rate

    • Sentinels fired (<!-- auto-rebase-conflict:): 136
    • Dev-lead rebase responses (intent=rebase): 29
    • Resolved & pushed (status=applied): 6
    • Resolution rate (responses Γ· sentinels): 21%
    • Applied rate (applied Γ· sentinels): 4%

    Auto-rebase fan-out volume (estimate)

    • Workflow runs (auto-rebase.yml): 62 total Β· 59 success Β· 0 failed
    • Behind-PR multiplier (open non-Dependabot PRs): 19
    • Estimated branch-update CI re-runs: ~1178
    • Per-day baseline: 8.9 auto-rebase run(s)/day Β· ~168.3 CI re-run(s)/day

    Fan-out is an estimate β€” per-run behind-PR counts are not logged in this repo, so re-runs = runs Γ— current open non-Dependabot PR count.

    Fleet merge-state observability (AC7)

    • BEHIND (open non-draft non-Dependabot PRs mergeStateStatus: BEHIND): 0
    • DIRTY (open non-draft non-Dependabot PRs mergeStateStatus: DIRTY): 5

    Snapshot of the current open-PR queue, scoped to petry-projects/.github-private β€” fleet-wide counts would require a cross-repo PAT this report does not carry. Tracks the effectiveness of the AC1/AC2 auto-rebase fixes (combsmith/.github#926) without a manual audit.

    Base-merge necessity (#1881)

    • Up-to-date-branches policy (ruleset strict_required_status_checks_policy): false
    • Base merges required (behind actually blocks: strict on, enqueued in merge queue, or auto-rebase:ready label): 0
    • Base merges skippable (BEHIND with no such requirement β€” a no-op churn): 0
    • base_merges_required=0 base_merges_skippable=0

    Deterministic counter over open non-draft non-Dependabot BEHIND PRs (DIRTY PRs keep the conflict/rebase path, so they are excluded). skippable is the no-op base-merge volume #1881 removes at the source; it is the second input to #1864 AC #4 alongside #1865 reviews_carried_forward. The policy flag is read from repository configuration β€” if strict is re-armed, every BEHIND PR becomes required with no code change.

  17. github-actions commented on Oct 12, 2026

    @github-actions
    ContributorAuthor

    πŸ” Auto-rebase Health β€” 2026-10-12

    Repo petry-projects/.github-private Β· lookback 7 day(s)

    Agentic conflict-resolution rate

    • Sentinels fired (<!-- auto-rebase-conflict:): 213
    • Dev-lead rebase responses (intent=rebase): 34
    • Resolved & pushed (status=applied): 11
    • Resolution rate (responses Γ· sentinels): 15%
    • Applied rate (applied Γ· sentinels): 5%

    Auto-rebase fan-out volume (estimate)

    • Workflow runs (auto-rebase.yml): 82 total Β· 76 success Β· 0 failed
    • Behind-PR multiplier (open non-Dependabot PRs): 16
    • Estimated branch-update CI re-runs: ~1312
    • Per-day baseline: 11.7 auto-rebase run(s)/day Β· ~187.4 CI re-run(s)/day

    Fan-out is an estimate β€” per-run behind-PR counts are not logged in this repo, so re-runs = runs Γ— current open non-Dependabot PR count.

    Fleet merge-state observability (AC7)

    • BEHIND (open non-draft non-Dependabot PRs mergeStateStatus: BEHIND): 0
    • DIRTY (open non-draft non-Dependabot PRs mergeStateStatus: DIRTY): 4

    Snapshot of the current open-PR queue, scoped to petry-projects/.github-private β€” fleet-wide counts would require a cross-repo PAT this report does not carry. Tracks the effectiveness of the AC1/AC2 auto-rebase fixes (combsmith/.github#926) without a manual audit.

    Base-merge necessity (#1881)

    • Up-to-date-branches policy (ruleset strict_required_status_checks_policy): false
    • Base merges required (behind actually blocks: strict on, enqueued in merge queue, or auto-rebase:ready label): 0
    • Base merges skippable (BEHIND with no such requirement β€” a no-op churn): 0
    • base_merges_required=0 base_merges_skippable=0

    Deterministic counter over open non-draft non-Dependabot BEHIND PRs (DIRTY PRs keep the conflict/rebase path, so they are excluded). skippable is the no-op base-merge volume #1881 removes at the source; it is the second input to #1864 AC #4 alongside #1865 reviews_carried_forward. The policy flag is read from repository configuration β€” if strict is re-armed, every BEHIND PR becomes required with no code change.

  18. github-actions commented on Oct 13, 2026

    @github-actions
    ContributorAuthor

    πŸ” Auto-rebase Health β€” 2026-10-13

    Repo petry-projects/.github-private Β· lookback 7 day(s)

    Agentic conflict-resolution rate

    • Sentinels fired (<!-- auto-rebase-conflict:): 213
    • Dev-lead rebase responses (intent=rebase): 34
    • Resolved & pushed (status=applied): 11
    • Resolution rate (responses Γ· sentinels): 15%
    • Applied rate (applied Γ· sentinels): 5%

    Auto-rebase fan-out volume (estimate)

    • Workflow runs (auto-rebase.yml): 82 total Β· 76 success Β· 0 failed
    • Behind-PR multiplier (open non-Dependabot PRs): 16
    • Estimated branch-update CI re-runs: ~1312
    • Per-day baseline: 11.7 auto-rebase run(s)/day Β· ~187.4 CI re-run(s)/day

    Fan-out is an estimate β€” per-run behind-PR counts are not logged in this repo, so re-runs = runs Γ— current open non-Dependabot PR count.

    Fleet merge-state observability (AC7)

    • BEHIND (open non-draft non-Dependabot PRs mergeStateStatus: BEHIND): 0
    • DIRTY (open non-draft non-Dependabot PRs mergeStateStatus: DIRTY): 4

    Snapshot of the current open-PR queue, scoped to petry-projects/.github-private β€” fleet-wide counts would require a cross-repo PAT this report does not carry. Tracks the effectiveness of the AC1/AC2 auto-rebase fixes (combsmith/.github#926) without a manual audit.

    Base-merge necessity (#1881)

    • Up-to-date-branches policy (ruleset strict_required_status_checks_policy): false
    • Base merges required (behind actually blocks: strict on, enqueued in merge queue, or auto-rebase:ready label): 0
    • Base merges skippable (BEHIND with no such requirement β€” a no-op churn): 0
    • base_merges_required=0 base_merges_skippable=0

    Deterministic counter over open non-draft non-Dependabot BEHIND PRs (DIRTY PRs keep the conflict/rebase path, so they are excluded). skippable is the no-op base-merge volume #1881 removes at the source; it is the second input to #1864 AC #4 alongside #1865 reviews_carried_forward. The policy flag is read from repository configuration β€” if strict is re-armed, every BEHIND PR becomes required with no code change.

  19. github-actions commented on Oct 15, 2026

    @github-actions
    ContributorAuthor

    πŸ” Auto-rebase Health β€” 2026-10-15

    Repo combsmith/.github-private Β· lookback 7 day(s)

    Agentic conflict-resolution rate

    • Sentinels fired (<!-- auto-rebase-conflict:): 219
    • Dev-lead rebase responses (intent=rebase): 23
    • Resolved & pushed (status=applied): 11
    • Resolution rate (responses Γ· sentinels): 10%
    • Applied rate (applied Γ· sentinels): 5%

    Auto-rebase fan-out volume (estimate)

    • Workflow runs (auto-rebase.yml): 85 total Β· 79 success Β· 0 failed
    • Behind-PR multiplier (open non-Dependabot PRs): 15
    • Estimated branch-update CI re-runs: ~1275
    • Per-day baseline: 12.1 auto-rebase run(s)/day Β· ~182.1 CI re-run(s)/day

    Fan-out is an estimate β€” per-run behind-PR counts are not logged in this repo, so re-runs = runs Γ— current open non-Dependabot PR count.

    Fleet merge-state observability (AC7)

    • BEHIND (open non-draft non-Dependabot PRs mergeStateStatus: BEHIND): 0
    • DIRTY (open non-draft non-Dependabot PRs mergeStateStatus: DIRTY): 4

    Snapshot of the current open-PR queue, scoped to combsmith/.github-private β€” fleet-wide counts would require a cross-repo PAT this report does not carry. Tracks the effectiveness of the AC1/AC2 auto-rebase fixes (combsmith/.github#926) without a manual audit.

    Base-merge necessity (#1881)

    • Up-to-date-branches policy (ruleset strict_required_status_checks_policy): false
    • Base merges required (behind actually blocks: strict on, enqueued in merge queue, or auto-rebase:ready label): 0
    • Base merges skippable (BEHIND with no such requirement β€” a no-op churn): 0
    • base_merges_required=0 base_merges_skippable=0

    Deterministic counter over open non-draft non-Dependabot BEHIND PRs (DIRTY PRs keep the conflict/rebase path, so they are excluded). skippable is the no-op base-merge volume #1881 removes at the source; it is the second input to #1864 AC #4 alongside #1865 reviews_carried_forward. The policy flag is read from repository configuration β€” if strict is re-armed, every BEHIND PR becomes required with no code change.

  20. github-actions commented on Oct 16, 2026

    @github-actions
    ContributorAuthor

    πŸ” Auto-rebase Health β€” 2026-10-16

    Repo combsmith/.github-private Β· lookback 7 day(s)

    Agentic conflict-resolution rate

    • Sentinels fired (<!-- auto-rebase-conflict:): 204
    • Dev-lead rebase responses (intent=rebase): 20
    • Resolved & pushed (status=applied): 11
    • Resolution rate (responses Γ· sentinels): 9%
    • Applied rate (applied Γ· sentinels): 5%

    Auto-rebase fan-out volume (estimate)

    • Workflow runs (auto-rebase.yml): 78 total Β· 72 success Β· 0 failed
    • Behind-PR multiplier (open non-Dependabot PRs): 14
    • Estimated branch-update CI re-runs: ~1092
    • Per-day baseline: 11.1 auto-rebase run(s)/day Β· ~156.0 CI re-run(s)/day

    Fan-out is an estimate β€” per-run behind-PR counts are not logged in this repo, so re-runs = runs Γ— current open non-Dependabot PR count.

    Fleet merge-state observability (AC7)

    • BEHIND (open non-draft non-Dependabot PRs mergeStateStatus: BEHIND): 0
    • DIRTY (open non-draft non-Dependabot PRs mergeStateStatus: DIRTY): 4

    Snapshot of the current open-PR queue, scoped to combsmith/.github-private β€” fleet-wide counts would require a cross-repo PAT this report does not carry. Tracks the effectiveness of the AC1/AC2 auto-rebase fixes (combsmith/.github#926) without a manual audit.

    Base-merge necessity (#1881)

    • Up-to-date-branches policy (ruleset strict_required_status_checks_policy): false
    • Base merges required (behind actually blocks: strict on, enqueued in merge queue, or auto-rebase:ready label): 0
    • Base merges skippable (BEHIND with no such requirement β€” a no-op churn): 0
    • base_merges_required=0 base_merges_skippable=0

    Deterministic counter over open non-draft non-Dependabot BEHIND PRs (DIRTY PRs keep the conflict/rebase path, so they are excluded). skippable is the no-op base-merge volume #1881 removes at the source; it is the second input to #1864 AC #4 alongside #1865 reviews_carried_forward. The policy flag is read from repository configuration β€” if strict is re-armed, every BEHIND PR becomes required with no code change.

  21. github-actions commented on Oct 17, 2026

    @github-actions
    ContributorAuthor

    πŸ” Auto-rebase Health β€” 2026-10-17

    Repo combsmith/.github-private Β· lookback 7 day(s)

    Agentic conflict-resolution rate

    • Sentinels fired (<!-- auto-rebase-conflict:): 190
    • Dev-lead rebase responses (intent=rebase): 13
    • Resolved & pushed (status=applied): 11
    • Resolution rate (responses Γ· sentinels): 6%
    • Applied rate (applied Γ· sentinels): 5%

    Auto-rebase fan-out volume (estimate)

    • Workflow runs (auto-rebase.yml): 63 total Β· 57 success Β· 0 failed
    • Behind-PR multiplier (open non-Dependabot PRs): 13
    • Estimated branch-update CI re-runs: ~819
    • Per-day baseline: 9.0 auto-rebase run(s)/day Β· ~117.0 CI re-run(s)/day

    Fan-out is an estimate β€” per-run behind-PR counts are not logged in this repo, so re-runs = runs Γ— current open non-Dependabot PR count.

    Fleet merge-state observability (AC7)

    • BEHIND (open non-draft non-Dependabot PRs mergeStateStatus: BEHIND): 0
    • DIRTY (open non-draft non-Dependabot PRs mergeStateStatus: DIRTY): 4

    Snapshot of the current open-PR queue, scoped to combsmith/.github-private β€” fleet-wide counts would require a cross-repo PAT this report does not carry. Tracks the effectiveness of the AC1/AC2 auto-rebase fixes (combsmith/.github#926) without a manual audit.

    Base-merge necessity (#1881)

    • Up-to-date-branches policy (ruleset strict_required_status_checks_policy): false
    • Base merges required (behind actually blocks: strict on, enqueued in merge queue, or auto-rebase:ready label): 0
    • Base merges skippable (BEHIND with no such requirement β€” a no-op churn): 0
    • base_merges_required=0 base_merges_skippable=0

    Deterministic counter over open non-draft non-Dependabot BEHIND PRs (DIRTY PRs keep the conflict/rebase path, so they are excluded). skippable is the no-op base-merge volume #1881 removes at the source; it is the second input to #1864 AC #4 alongside #1865 reviews_carried_forward. The policy flag is read from repository configuration β€” if strict is re-armed, every BEHIND PR becomes required with no code change.

  22. github-actions commented on Oct 18, 2026

    @github-actions
    ContributorAuthor

    πŸ” Auto-rebase Health β€” 2026-10-18

    Repo combsmith/.github-private Β· lookback 7 day(s)

    Agentic conflict-resolution rate

    • Sentinels fired (<!-- auto-rebase-conflict:): 122
    • Dev-lead rebase responses (intent=rebase): 6
    • Resolved & pushed (status=applied): 6
    • Resolution rate (responses Γ· sentinels): 4%
    • Applied rate (applied Γ· sentinels): 4%

    Auto-rebase fan-out volume (estimate)

    • Workflow runs (auto-rebase.yml): 31 total Β· 28 success Β· 0 failed
    • Behind-PR multiplier (open non-Dependabot PRs): 13
    • Estimated branch-update CI re-runs: ~403
    • Per-day baseline: 4.4 auto-rebase run(s)/day Β· ~57.6 CI re-run(s)/day

    Fan-out is an estimate β€” per-run behind-PR counts are not logged in this repo, so re-runs = runs Γ— current open non-Dependabot PR count.

    Fleet merge-state observability (AC7)

    • BEHIND (open non-draft non-Dependabot PRs mergeStateStatus: BEHIND): 0
    • DIRTY (open non-draft non-Dependabot PRs mergeStateStatus: DIRTY): 4

    Snapshot of the current open-PR queue, scoped to combsmith/.github-private β€” fleet-wide counts would require a cross-repo PAT this report does not carry. Tracks the effectiveness of the AC1/AC2 auto-rebase fixes (combsmith/.github#926) without a manual audit.

    Base-merge necessity (#1881)

    • Up-to-date-branches policy (ruleset strict_required_status_checks_policy): false
    • Base merges required (behind actually blocks: strict on, enqueued in merge queue, or auto-rebase:ready label): 0
    • Base merges skippable (BEHIND with no such requirement β€” a no-op churn): 0
    • base_merges_required=0 base_merges_skippable=0

    Deterministic counter over open non-draft non-Dependabot BEHIND PRs (DIRTY PRs keep the conflict/rebase path, so they are excluded). skippable is the no-op base-merge volume #1881 removes at the source; it is the second input to #1864 AC #4 alongside #1865 reviews_carried_forward. The policy flag is read from repository configuration β€” if strict is re-armed, every BEHIND PR becomes required with no code change.

  23. github-actions commented on Oct 19, 2026

    @github-actions
    ContributorAuthor

    πŸ” Auto-rebase Health β€” 2026-10-19

    Repo combsmith/.github-private Β· lookback 7 day(s)

    Agentic conflict-resolution rate

    • Sentinels fired (<!-- auto-rebase-conflict:): 42
    • Dev-lead rebase responses (intent=rebase): 0
    • Resolved & pushed (status=applied): 0
    • Resolution rate (responses Γ· sentinels): 0%
    • Applied rate (applied Γ· sentinels): 0%

    Auto-rebase fan-out volume (estimate)

    • Workflow runs (auto-rebase.yml): 10 total Β· 10 success Β· 0 failed
    • Behind-PR multiplier (open non-Dependabot PRs): 13
    • Estimated branch-update CI re-runs: ~130
    • Per-day baseline: 1.4 auto-rebase run(s)/day Β· ~18.6 CI re-run(s)/day

    Fan-out is an estimate β€” per-run behind-PR counts are not logged in this repo, so re-runs = runs Γ— current open non-Dependabot PR count.

    Fleet merge-state observability (AC7)

    • BEHIND (open non-draft non-Dependabot PRs mergeStateStatus: BEHIND): 0
    • DIRTY (open non-draft non-Dependabot PRs mergeStateStatus: DIRTY): 4

    Snapshot of the current open-PR queue, scoped to combsmith/.github-private β€” fleet-wide counts would require a cross-repo PAT this report does not carry. Tracks the effectiveness of the AC1/AC2 auto-rebase fixes (combsmith/.github#926) without a manual audit.

    Base-merge necessity (#1881)

    • Up-to-date-branches policy (ruleset strict_required_status_checks_policy): false
    • Base merges required (behind actually blocks: strict on, enqueued in merge queue, or auto-rebase:ready label): 0
    • Base merges skippable (BEHIND with no such requirement β€” a no-op churn): 0
    • base_merges_required=0 base_merges_skippable=0

    Deterministic counter over open non-draft non-Dependabot BEHIND PRs (DIRTY PRs keep the conflict/rebase path, so they are excluded). skippable is the no-op base-merge volume #1881 removes at the source; it is the second input to #1864 AC #4 alongside #1865 reviews_carried_forward. The policy flag is read from repository configuration β€” if strict is re-armed, every BEHIND PR becomes required with no code change.

  24. github-actions commented on Oct 20, 2026

    @github-actions
    ContributorAuthor

    πŸ” Auto-rebase Health β€” 2026-10-20

    Repo combsmith/.github-private Β· lookback 7 day(s)

    Agentic conflict-resolution rate

    • Sentinels fired (<!-- auto-rebase-conflict:): 42
    • Dev-lead rebase responses (intent=rebase): 0
    • Resolved & pushed (status=applied): 0
    • Resolution rate (responses Γ· sentinels): 0%
    • Applied rate (applied Γ· sentinels): 0%

    Auto-rebase fan-out volume (estimate)

    • Workflow runs (auto-rebase.yml): 10 total Β· 10 success Β· 0 failed
    • Behind-PR multiplier (open non-Dependabot PRs): 17
    • Estimated branch-update CI re-runs: ~170
    • Per-day baseline: 1.4 auto-rebase run(s)/day Β· ~24.3 CI re-run(s)/day

    Fan-out is an estimate β€” per-run behind-PR counts are not logged in this repo, so re-runs = runs Γ— current open non-Dependabot PR count.

    Fleet merge-state observability (AC7)

    • BEHIND (open non-draft non-Dependabot PRs mergeStateStatus: BEHIND): 0
    • DIRTY (open non-draft non-Dependabot PRs mergeStateStatus: DIRTY): 4

    Snapshot of the current open-PR queue, scoped to combsmith/.github-private β€” fleet-wide counts would require a cross-repo PAT this report does not carry. Tracks the effectiveness of the AC1/AC2 auto-rebase fixes (combsmith/.github#926) without a manual audit.

    Base-merge necessity (#1881)

    • Up-to-date-branches policy (ruleset strict_required_status_checks_policy): false
    • Base merges required (behind actually blocks: strict on, enqueued in merge queue, or auto-rebase:ready label): 0
    • Base merges skippable (BEHIND with no such requirement β€” a no-op churn): 0
    • base_merges_required=0 base_merges_skippable=0

    Deterministic counter over open non-draft non-Dependabot BEHIND PRs (DIRTY PRs keep the conflict/rebase path, so they are excluded). skippable is the no-op base-merge volume #1881 removes at the source; it is the second input to #1864 AC #4 alongside #1865 reviews_carried_forward. The policy flag is read from repository configuration β€” if strict is re-armed, every BEHIND PR becomes required with no code change.

  25. github-actions commented on Oct 21, 2026

    @github-actions
    ContributorAuthor

    πŸ” Auto-rebase Health β€” 2026-10-21

    Repo combsmith/.github-private Β· lookback 7 day(s)

    Agentic conflict-resolution rate

    • Sentinels fired (<!-- auto-rebase-conflict:): 63
    • Dev-lead rebase responses (intent=rebase): 0
    • Resolved & pushed (status=applied): 0
    • Resolution rate (responses Γ· sentinels): 0%
    • Applied rate (applied Γ· sentinels): 0%

    Auto-rebase fan-out volume (estimate)

    • Workflow runs (auto-rebase.yml): 14 total Β· 14 success Β· 0 failed
    • Behind-PR multiplier (open non-Dependabot PRs): 15
    • Estimated branch-update CI re-runs: ~210
    • Per-day baseline: 2.0 auto-rebase run(s)/day Β· ~30.0 CI re-run(s)/day

    Fan-out is an estimate β€” per-run behind-PR counts are not logged in this repo, so re-runs = runs Γ— current open non-Dependabot PR count.

    Fleet merge-state observability (AC7)

    • BEHIND (open non-draft non-Dependabot PRs mergeStateStatus: BEHIND): 0
    • DIRTY (open non-draft non-Dependabot PRs mergeStateStatus: DIRTY): 5

    Snapshot of the current open-PR queue, scoped to combsmith/.github-private β€” fleet-wide counts would require a cross-repo PAT this report does not carry. Tracks the effectiveness of the AC1/AC2 auto-rebase fixes (combsmith/.github#926) without a manual audit.

    Base-merge necessity (#1881)

    • Up-to-date-branches policy (ruleset strict_required_status_checks_policy): false
    • Base merges required (behind actually blocks: strict on, enqueued in merge queue, or auto-rebase:ready label): 0
    • Base merges skippable (BEHIND with no such requirement β€” a no-op churn): 0
    • base_merges_required=0 base_merges_skippable=0

    Deterministic counter over open non-draft non-Dependabot BEHIND PRs (DIRTY PRs keep the conflict/rebase path, so they are excluded). skippable is the no-op base-merge volume #1881 removes at the source; it is the second input to #1864 AC #4 alongside #1865 reviews_carried_forward. The policy flag is read from repository configuration β€” if strict is re-armed, every BEHIND PR becomes required with no code change.

  26. github-actions commented on Oct 22, 2026

    @github-actions
    ContributorAuthor

    πŸ” Auto-rebase Health β€” 2026-10-22

    Repo combsmith/.github-private Β· lookback 7 day(s)

    Agentic conflict-resolution rate

    • Sentinels fired (<!-- auto-rebase-conflict:): 53
    • Dev-lead rebase responses (intent=rebase): 0
    • Resolved & pushed (status=applied): 0
    • Resolution rate (responses Γ· sentinels): 0%
    • Applied rate (applied Γ· sentinels): 0%

    Auto-rebase fan-out volume (estimate)

    • Workflow runs (auto-rebase.yml): 11 total Β· 11 success Β· 0 failed
    • Behind-PR multiplier (open non-Dependabot PRs): 15
    • Estimated branch-update CI re-runs: ~165
    • Per-day baseline: 1.6 auto-rebase run(s)/day Β· ~23.6 CI re-run(s)/day

    Fan-out is an estimate β€” per-run behind-PR counts are not logged in this repo, so re-runs = runs Γ— current open non-Dependabot PR count.

    Fleet merge-state observability (AC7)

    • BEHIND (open non-draft non-Dependabot PRs mergeStateStatus: BEHIND): 0
    • DIRTY (open non-draft non-Dependabot PRs mergeStateStatus: DIRTY): 5

    Snapshot of the current open-PR queue, scoped to combsmith/.github-private β€” fleet-wide counts would require a cross-repo PAT this report does not carry. Tracks the effectiveness of the AC1/AC2 auto-rebase fixes (combsmith/.github#926) without a manual audit.

    Base-merge necessity (#1881)

    • Up-to-date-branches policy (ruleset strict_required_status_checks_policy): false
    • Base merges required (behind actually blocks: strict on, enqueued in merge queue, or auto-rebase:ready label): 0
    • Base merges skippable (BEHIND with no such requirement β€” a no-op churn): 0
    • base_merges_required=0 base_merges_skippable=0

    Deterministic counter over open non-draft non-Dependabot BEHIND PRs (DIRTY PRs keep the conflict/rebase path, so they are excluded). skippable is the no-op base-merge volume #1881 removes at the source; it is the second input to #1864 AC #4 alongside #1865 reviews_carried_forward. The policy flag is read from repository configuration β€” if strict is re-armed, every BEHIND PR becomes required with no code change.

  27. github-actions commented on Oct 23, 2026

    @github-actions
    ContributorAuthor

    πŸ” Auto-rebase Health β€” 2026-10-23

    Repo combsmith/.github-private Β· lookback 7 day(s)

    Agentic conflict-resolution rate

    • Sentinels fired (<!-- auto-rebase-conflict:): 54
    • Dev-lead rebase responses (intent=rebase): 0
    • Resolved & pushed (status=applied): 0
    • Resolution rate (responses Γ· sentinels): 0%
    • Applied rate (applied Γ· sentinels): 0%

    Auto-rebase fan-out volume (estimate)

    • Workflow runs (auto-rebase.yml): 11 total Β· 11 success Β· 0 failed
    • Behind-PR multiplier (open non-Dependabot PRs): 15
    • Estimated branch-update CI re-runs: ~165
    • Per-day baseline: 1.6 auto-rebase run(s)/day Β· ~23.6 CI re-run(s)/day

    Fan-out is an estimate β€” per-run behind-PR counts are not logged in this repo, so re-runs = runs Γ— current open non-Dependabot PR count.

    Fleet merge-state observability (AC7)

    • BEHIND (open non-draft non-Dependabot PRs mergeStateStatus: BEHIND): 0
    • DIRTY (open non-draft non-Dependabot PRs mergeStateStatus: DIRTY): 5

    Snapshot of the current open-PR queue, scoped to combsmith/.github-private β€” fleet-wide counts would require a cross-repo PAT this report does not carry. Tracks the effectiveness of the AC1/AC2 auto-rebase fixes (combsmith/.github#926) without a manual audit.

    Base-merge necessity (#1881)

    • Up-to-date-branches policy (ruleset strict_required_status_checks_policy): false
    • Base merges required (behind actually blocks: strict on, enqueued in merge queue, or auto-rebase:ready label): 0
    • Base merges skippable (BEHIND with no such requirement β€” a no-op churn): 0
    • base_merges_required=0 base_merges_skippable=0

    Deterministic counter over open non-draft non-Dependabot BEHIND PRs (DIRTY PRs keep the conflict/rebase path, so they are excluded). skippable is the no-op base-merge volume #1881 removes at the source; it is the second input to #1864 AC #4 alongside #1865 reviews_carried_forward. The policy flag is read from repository configuration β€” if strict is re-armed, every BEHIND PR becomes required with no code change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    auto-rebase-healthDaily auto-rebase instrumentation report

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions