Skip to content

Fix garminctl description (drop bug-fix claim, position vs go-garmin) - #80

Closed
jjuanrivvera99 wants to merge 2 commits into
mainfrom
feature/add-garminctl-project
Closed

Fix garminctl description (drop bug-fix claim, position vs go-garmin)#80
jjuanrivvera99 wants to merge 2 commits into
mainfrom
feature/add-garminctl-project

Conversation

@jjuanrivvera99

Copy link
Copy Markdown
Member

Follow-up to #78. The garminctl description claimed it "fixes the recurring authentication failure" — but go-garmin (the upstream library) already handles the OAuth refresh, and go-garmin is itself a broader CLI. Reword the en/es/pt descriptions to say what garminctl actually adds: keyring token storage vs a plaintext session file, named profiles, and garth import.

pnpm check passes (0 errors/warnings/hints).

garminctl — Garmin Connect CLI wrapping go-garmin with keyring auth (automatic token
refresh), named profiles, and an MCP server. Released v0.1.0 with Homebrew + Scoop and a
docs site. Added as a non-featured project with en/es/pt descriptions.
go-garmin already handles the OAuth refresh and is itself a broader CLI. Describe what garminctl
adds instead: keyring storage vs a plaintext session file, named profiles, garth import.
@coderabbitai

coderabbitai Bot commented Jul 12, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@jjuanrivvera99, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 23 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 94b40a72-aebc-44b1-b9a5-6a03f9c4d0c1

📥 Commits

Reviewing files that changed from the base of the PR and between f4e1d98 and 855f368.

📒 Files selected for processing (2)
  • src/config/projects.ts
  • src/i18n/ui.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feature/add-garminctl-project

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.

@netlify

netlify Bot commented Jul 12, 2026

Copy link
Copy Markdown

Deploy Preview for jjuanrivvera99 ready!

Name Link
🔨 Latest commit 855f368
🔍 Latest deploy log https://app.netlify.com/projects/jjuanrivvera99/deploys/6a52ecad385d0900085122b7
😎 Deploy Preview https://deploy-preview-80--jjuanrivvera99.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@jjuanrivvera99

Copy link
Copy Markdown
Member Author

Superseded by a clean fresh-branch PR (the source branch had diverged after the squash-merge of #78).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant