Skip to content

Separate accounts in usage tables - #15

Merged
ygpark80 merged 1 commit into
mainfrom
feat/usage-account-separators
Aug 10, 2026
Merged

Separate accounts in usage tables#15
ygpark80 merged 1 commit into
mainfrom
feat/usage-account-separators

Conversation

@ygpark80

@ygpark80 ygpark80 commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

User description

Changes

  • add a horizontal divider whenever the usage table moves to another account
  • keep limits within the same account visually grouped

Testing

  • go test -mod=vendor -race ./...
  • go vet -mod=vendor ./...
  • Linux and macOS CGO-disabled builds
  • live ChatGPT usage output with three accounts

CodeAnt-AI Description

Visually separate usage data for different accounts

What Changed

  • Usage tables now show a horizontal divider before each account that has limits or an error
  • Limits belonging to the same account remain grouped together
  • Accounts with usage errors are clearly separated from the preceding account’s data

Impact

✅ Clearer multi-account usage tables
✅ Easier account-by-account limit comparison
✅ More visible usage errors

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

Summary by CodeRabbit

  • Improvements
    • Improved usage table formatting by adding separator lines between accounts when displaying errors or multiple limits.
    • Updated usage output to make account boundaries clearer and easier to read.

@codeant-ai

codeant-ai Bot commented Aug 10, 2026

Copy link
Copy Markdown

🤖 CodeAnt AI — Review Status

Status Commit Started (UTC) Finished (UTC)
✅ Reviewed your PR ec268d1 Aug 10, 2026 · 03:20 03:22

@codeant-ai

codeant-ai Bot commented Aug 10, 2026

Copy link
Copy Markdown

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

@coderabbitai

coderabbitai Bot commented Aug 10, 2026

Copy link
Copy Markdown

Review Change Stack

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: b2ba9cc0-6d25-4444-9465-d01f529b7bba

📥 Commits

Reviewing files that changed from the base of the PR and between 7ca641c and ec268d1.

📒 Files selected for processing (2)
  • internal/cli/run.go
  • internal/cli/run_test.go

📝 Walkthrough

Walkthrough

The usage table now tracks account boundaries that need visual separators. printTable renders borders before those rows. The ChatGPT usage output test includes the new separator.

Changes

Usage table rendering

Layer / File(s) Summary
Account separator rendering
internal/cli/run.go, internal/cli/run_test.go
printUsageAt identifies account boundaries for accounts with errors or multiple limits. printTable renders borders before those rows. The usage output test expects the separator.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/usage-account-separators

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@codeant-ai codeant-ai Bot added the size:S This PR changes 10-29 lines, ignoring generated files label Aug 10, 2026
@ygpark80
ygpark80 merged commit 93ec793 into main Aug 10, 2026
1 check passed
@ygpark80
ygpark80 deleted the feat/usage-account-separators branch August 10, 2026 03:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:S This PR changes 10-29 lines, ignoring generated files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant