Add status page incident event commands - #57
Merged
Conversation
Member
Author
Greptile SummaryThe PR adds status-page discovery and incident-event lifecycle commands to the CLI.
Confidence Score: 5/5The PR appears safe to merge. No blocking failure remains. Important Files Changed
Reviews (5): Last reviewed commit: "validate status page pagination" | Re-trigger Greptile |
Member
Author
1 similar comment
Member
Author
kwent
marked this pull request as ready for review
August 13, 2026 04:07
kwent
force-pushed
the
agent/status-page-events
branch
from
August 13, 2026 04:09
d8669b7 to
c1461a1
Compare
Member
Author
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
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.
Summary
status-pagesresource group with paginated discovery using the same--name,--slug, sorting, and output conventions as neighboring commands--started-atcontrols where the server implements themInterface
--notify-subscribersis intentionally create-only: the server notification callback does not run for event updates. Tweeting is not exposed because the API controller does not accept the documented field, and component selection remains out of scope because it is feature-gated and requires component discovery.Closes #52
Testing
go test ./...git diff --check