[stale-pr] mctl-gitops#306: fix(observability): prometheus-pushgateway into gitops — 13 days no activity #405

Activity

1. mashkovd

   added

   stale-pr

   on Jun 7, 2026
2. mashkovd commented on Jun 10, 2026

   

   mashkovd

   on Jun 10, 2026 – with Claude

   MemberAuthor

   More actions

   Daily-report follow-up — 2026-06-10 (day 16)

   mctl-gitops#306 fix(observability): bring prometheus-pushgateway into gitops + fix scrape config is still open — 16 days without activity. June 9 daily-report was skipped.

   Daily-report: #411

   ---

   Generated by Claude Code
3. mashkovd commented on Jun 11, 2026

   

   mashkovd

   on Jun 11, 2026 – with Claude

   MemberAuthor

   More actions

   Daily-report 2026-06-11: mctl-gitops#306 still open — 17 days without activity (was 16 d). No change since #411.

   ---

   Generated by Claude Code
4. mashkovd commented on Jun 13, 2026

   

   mashkovd

   on Jun 13, 2026 – with Claude

   MemberAuthor

   More actions

   Daily-report update — 2026-06-13 (#421)

   mctl-gitops#306 (fix(observability): bring prometheus-pushgateway into gitops) still open with no new activity — 19 days stale (last updated 2026-05-25).

   2-day gap since last update: 2026-06-12 report was skipped.

   ---

   Generated by Claude Code
5. mashkovd commented on Jun 14, 2026

   

   mashkovd

   on Jun 14, 2026 – with Claude

   MemberAuthor

   More actions

   Daily check-in 2026-06-14 — still stale. mctl-gitops#306 fix(observability): bring prometheus-pushgateway into gitops + fix scrape — no activity for 20 days (last update 2026-05-25). No change since last report (#421, 2026-06-13).

   ---

   Generated by Claude Code
6. mashkovd commented on Sep 10, 2026

   

   mashkovd

   on Sep 10, 2026

   MemberAuthor

   More actions

   Closing: the PR this tracks, mctl-gitops#306, was merged on 2026-07-02 — over two months ago. There is nothing dormant left to chase.

   Worth recording that this is not one stray issue. Resolving every open [stale-pr] tracker against its subject PR:

   open [stale-pr] trackers:  43
     subject PR already merged/closed (orphaned):  41
     subject PR still open (live):                  2   (both mctl-pairdesk#57 — duplicates of each other)
   

   So 41 of 43 are residue. Two further observations about the automation that produced them:

   • It no longer runs. Oldest tracker 2026-05-31, newest 2026-07-09; nothing since. No workflow under .github/ in this repo (or anywhere in the workspace) creates or reaps them.
   • It never closed its own trackers on resolution. A handful were closed by hand around 2026-05-30 ([stale-pr] mctl-agents#15: feat(orchestrator): Tier 2 implementer agents #228, [stale-pr] mctl-web#12: feat: redesign v3 — 8 days dormant #297, [stale-pr] mctl-telegram#146: Enhance landing page UX — 8 days dormant #337) and then the practice stopped. The trackers do not reference each other either, so the same PR accumulated several: mctl-gitops#84 has four ([stale-pr] mctl-gitops#84: [wip] per-proposal claim mechanism — 32 days dormant #358, [stale-pr] mctl-gitops#84: [wip] per-proposal claim mechanism — 37 days no activity #392, [stale-pr] mctl-gitops#84: [wip] feat(agents): per-proposal claim mechanism (50 days) #431, [stale-pr] mctl-gitops#84: [wip] per-proposal claim mechanism (52 days) #446), mctl-agents#15 has four, mctl-portal#7 has three.

   Since the producer is dead, closing these cannot race anything — but it is 40 more issues and not what this one was about, so they are left open pending a decision rather than swept here.

   Found while verifying #1159, which touched the same pushgateway component this PR introduced.
7. mashkovd

   closed this as not plannedon Sep 10, 2026