Skip to content

feat: living status comment for upstream PR maintenance #132

Open

Description

@diberry

Problem

Upstream PR maintenance comments go stale. Ralph posts "Waiting for CI" but when CI passes minutes later, the comment stays forever — misleading maintainers into thinking the PR isn't ready.

Example: https://github.com/bradygaster/squad/pull/726#issuecomment-4166475297

Solution: Living Status Comment

Use a single "living" comment per upstream PR that gets updated in-place on every Ralph loop, instead of appending new comments that go stale.

Pattern

  1. Search PR comments for <!-- ralph-upstream-status -->
  2. If found → gh api PATCH to update body with current state
  3. If not found → gh pr comment to create with marker
  4. Body always reflects CURRENT state:
<!-- ralph-upstream-status -->
## Upstream Maintenance Status
**Last checked:** {ISO 8601 timestamp}

- [x] Mergeable: MERGEABLE
- [x] Single commit
- [x] File audit: clean
- [x] CI: All checks green
- [x] Team approval: Reviewed on fork
- [x] Maintainer feedback: none

**Status:** Ready for maintainer review

Rules

  • ONE status comment per PR — never post a second
  • Update timestamp and checklist on every Ralph loop
  • Keep historical action comments (team reviews, changeset additions) as separate comments — do NOT merge those into the status comment
  • <!-- ralph-upstream-status --> marker MUST be on line 1

Where to implement

Update dina-upstream-pr-maintenance skill on diberry/squad branch:

.copilot/skills/dina-upstream-pr-maintenance/SKILL.md

gh API commands

Find existing comment:

gh api repos/{owner}/{repo}/issues/{pr_number}/comments --jq '.[] | select(.body | contains("<!-- ralph-upstream-status -->")) | .id'

Update comment:

gh api repos/{owner}/{repo}/issues/comments/{comment_id} -X PATCH -f body="..."

Create comment:

gh pr comment {pr_number} --repo {owner}/{repo} --body "..."

Activity

  1. added
    enhancementNew feature or request
    squadSquad triage inbox — Lead will assign to a member
    squad:flightAssigned to Flight (Lead)
    on Apr 1, 2026
  2. github-actions commented on Apr 1, 2026

    @github-actions

    📋 Assigned to Flight (Lead)

    Issue: #132 — feat: living status comment for upstream PR maintenance

    Flight will pick this up in the next Copilot session.

    For Copilot coding agent: If enabled, this issue will be worked automatically.
    Otherwise, start a Copilot session and say:
    Flight, work on issue #132

  3. github-actions commented on Apr 1, 2026

    @github-actions

    🏗️ Squad Triage — Flight (Lead)

    Issue: #132 — feat: living status comment for upstream PR maintenance
    Assigned to: Flight (Lead)
    Reason: No specific domain match — assigned to Lead for further analysis

    @copilot evaluation: 🔴 Not suitable — issue involves work outside the coding agent's capability profile.

    Team roster:

    • Flight (Lead) → label: squad:flight
    • Procedures (Prompt Engineer) → label: squad:procedures
    • EECOM (Core Dev) → label: squad:eecom
    • FIDO (Quality Owner) → label: squad:fido
    • PAO (DevRel) → label: squad:pao
    • CAPCOM (SDK Expert) → label: squad:capcom
    • CONTROL (TypeScript Engineer) → label: squad:control
    • Surgeon (Release Manager) → label: squad:surgeon
    • Booster (CI/CD Engineer) → label: squad:booster
    • GNC (Node.js Runtime) → label: squad:gnc
    • Network (Distribution) → label: squad:network
    • RETRO (Security) → label: squad:retro
    • INCO (CLI UX & Visual Design) → label: squad:inco
    • GUIDO (VS Code Extension) → label: squad:guido
    • Telemetry (Aspire & Observability) → label: squad:telemetry
    • VOX (REPL & Interactive Shell) → label: squad:vox
    • DSKY (TUI Engineer) → label: squad:dsky
    • Sims (E2E Test Engineer) → label: squad:sims
    • Handbook (SDK Usability) → label: squad:handbook
    • Ralph (Work Monitor) → label: squad:ralph
    • @copilot (Coding Agent) → label: squad:copilot

    To reassign, remove the current squad:* label and add the correct one.

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

    enhancementNew feature or requestgo:needs-researchNeeds investigationsquadSquad triage inbox — Lead will assign to a membersquad:flightAssigned to Flight (Lead)

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions