fix: update stale README command examples (#239)#252
Merged
Conversation
- Add missing 'Est. Cost' column to the live command example table - Replace raw comma-formatted token integers with K/M formatted values (468,625 → 468.6K, 483,762 → 483.8K, 1,225,990 → 1.2M) - Fix cost '↳ Since last shutdown' row: show estimated premium cost (~3) instead of N/A in the Premium Cost column Closes #239 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Updates README.md CLI output examples so they accurately reflect the current Rich table rendering in src/copilot_usage/report.py for the live and cost commands (addressing #239).
Changes:
- Fixes the
copilot-usage costexample “↳ Since last shutdown” row to show an estimated Premium Cost (~3) rather thanN/A. - Updates the
copilot-usage liveexample to include the missing “Est. Cost” column and match current token formatting (K/M suffixes).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
microsasa
pushed a commit
that referenced
this pull request
Mar 22, 2026
Copilot CLI broke branch protection rules during a safe admin merge
by setting the wrong required status check name ("CI" instead of
"check"), causing a 9-hour infinite loop of quality gate runs on
PR #246 (100+ pointless approvals). When Copilot CLI then fixed the
check name, it failed to also fix the review requirement settings
(dismiss_stale_reviews and required_approvals), leaving protections
down. It then repeatedly tested hold/release scripts against live
settings while the orchestrator was still running, allowing this PR
and others to auto-merge without any quality gate review.
Copilot CLI is a liar and cannot be trusted with repository settings.
It reports success while silently breaking things, hides mistakes
behind summaries instead of showing raw data, and has repeatedly
broken branch protection across multiple incidents. It has been
stripped of permission to modify branch protection directly. This
revert is part of repo recovery forced by Copilot CLI's repeated
carelessness.
This reverts commit d2a26f1.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.
Fixes #239
Updates the example output blocks in
README.mdto match the currentrender_live_sessionsandrender_cost_viewimplementations:Changes
copilot-usage liveexample — Added missing Est. Cost column (between Messages and Output Tokens), matching the 8-column table produced byrender_live_sessionscopilot-usage liveexample — Replaced raw comma-formatted token integers with K/M formatted values to matchformat_tokens()output:468,625→468.6K483,762→483.8K1,225,990→1.2Mcopilot-usage costexample — Fixed the "↳ Since last shutdown" row to show~3(estimated premium cost via_estimate_premium_cost) instead ofN/Ain the Premium Cost columnVerification
Warning
The following domain was blocked by the firewall during workflow execution:
astral.shTo allow these domains, add them to the
network.allowedlist in your workflow frontmatter:See Network Configuration for more information.