feat(github): decay progress-comment edit cadence as the comment ages#758
Draft
aparajon wants to merge 1 commit into
Draft
feat(github): decay progress-comment edit cadence as the comment ages#758aparajon wants to merge 1 commit into
aparajon wants to merge 1 commit into
Conversation
aparajon
force-pushed
the
armand/progress-comment-decay
branch
2 times, most recently
from
July 18, 2026 23:14
8e1ab8f to
0710f5b
Compare
A progress comment edits every 5s for its entire life, so a week-long
row copy makes hundreds of GitHub writes per hour against the
installation's shared budget long after anyone is watching the PR. The
edit interval now grows with the age of the live progress comment
(seconds-fresh -> minutes-old applies edit a few times per hour), while
state changes always publish immediately and the CLI remains the
high-resolution progress surface. Rotations (resume, volume change)
post a fresh comment and restart at the fastest cadence, since a
rotation means someone just acted on the apply.
The comment also states its own cadence: the "Last updated" footer
renders the current edit interval ("updates every ~2m") so a reader
watching a long apply sees the widening gap between updates as designed
behavior rather than a stall.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
aparajon
force-pushed
the
armand/progress-comment-dedupe
branch
from
July 19, 2026 00:04
76f5734 to
290a5dd
Compare
aparajon
force-pushed
the
armand/progress-comment-decay
branch
from
July 19, 2026 00:04
0710f5b to
389522a
Compare
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.
Why this matters
An actively copying apply edits its PR progress comment every 5 seconds — ~720 writes per hour, per apply, for as long as the copy runs. Nobody watches a PR comment continuously for a day, and a single week-long schema change can, by itself, keep the installation near GitHub's secondary content-creation limit. The CLI is the high-resolution progress surface; the PR comment needs to stay current, not real-time.
What it does
Spaces progress-comment edits further apart as the live progress comment ages:
· updates every ~2mfor the current rung, so a reader watching a long apply sees the widening gap as designed behavior rather than a stall. The note re-renders once at each rung transition, keeping the advertised cadence truthful.Stacked on #757.
🤖 Generated with Claude Code