Repository navigation
fix(dashboard): align action labels and sentence case - #1083
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
|
The latest updates on your projects. Learn more about Unkey Deploy
|
Contributor
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (120)
Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 0 remain after this review. 📜 Recent review details⏰ Context from checks skipped due to timeout. (1)
🧰 Additional context used📚 Code guidelines (3)📓 Path-based instructions (3)Source excerpt: When you discover a new performance improvement, optimization pattern, or fix a performance regression, add a concise bullet to the relevant section below in the same session.📄 CodeRabbit inference engine (.cursor/rules/performance.mdc) Files:
Source excerpt: MUST use Tailwind CSS defaults unless custom values already exist or are explicitly requested Source excerpt: MUST use motion/react (formerly framer-motion) when JavaScript animation is required Source excerpt: SHOULD use tw...📄 CodeRabbit inference engine (.cursor/rules/ui-guidelines.mdc) Files:
Source excerpt: description: Basic guidelines for the project so vibe coders don't fuck it up globs: alwaysApply: true when using 'text-right', always add 'text-balance' so its not ugly Source excerpt: description: Basic guidelines for the...📄 CodeRabbit inference engine (.cursor/rules/01-MUST-DO.mdc) Files:
🔇 Additional comments (63)
WalkthroughThe dashboard updates sentence-style capitalization, punctuation, labels, and selected badge displays across many pages and shared components. It also adjusts formatting for unrecognized invoice statuses, error severity labels, and long goal targets. E2E selectors now match the revised UI labels. ChangesDashboard labels and page displays
Priority: ⬇️ Low Estimated code review effort: 3 (Moderate) | ~25 minutes Change: Other Merge Risk: ⚪ Minimal · up to The reported misleading empty state does not occur for valid selected date ranges. No actionable merge-blocking issue remains after normal checks. 🚥 Pre-merge checks | ✅ 4 | ❓ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 2.27% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 44 functions across 50 files. (70 skipped: 1 unsupported, 69 over the file limit.) ✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
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. Comment |
This comment has been minimized.
This comment has been minimized.
izadoesdev
marked this pull request as ready for review
October 5, 2026 09:52
Member
Author
|
Please re-review final head |
Contributor
 |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Member
Author
|
Please re-review final head |
izadoesdev
force-pushed
the
codex/dashboard-copy
branch
from
October 6, 2026 06:50
c7ad920 to
e76cd95
Compare
izadoesdev
force-pushed
the
codex/dashboard-copy
branch
from
October 6, 2026 07:08
e76cd95 to
fff667f
Compare
Member
Author
|
Approval recovery disposition for The fresh review's general concern describes an existing limitation of #1072: an approval is claimed before message conversion and agent startup, so an early failure can consume an unused approval until expiry. The supported recovery is to verify the action state and obtain a fresh approval. This was documented in the approval review; the dashboard copy slice preserves all four approval implementation/test files byte for byte. The claim remains consumed after uncertain execution to prevent duplicate writes. The native regression specifically proves retention when the model fails after a successful approved write; it does not claim pre-execution recovery. In the installed SDK, local approved tools run before the model stream starts, so a model-stream failure alone does not establish that the action never ran. A blanket release on stream failure would re-enable replay after successful writes. I am declining a change to approval outcome/retry semantics in this copy slice. The before-execution recovery limitation remains explicit, and any stronger outcome/retry behavior needs an independently reviewed technical slice. |
Member
Author
|
@coderabbitai full review Please review all 120 scoped files at final head |
Contributor
✅ Action performedFull review finished. |
Member
Author
|
Please re-review final head |
Member
Author
|
Docstring advisory disposition for the completed source review at The full CodeRabbit review actually selected and reviewed all 120 owned paths and found no actionable issues. Its separate generic docstring check analyzed 44 functions across 50 files, skipped 69 files because of that check's own limit, and reported an inconclusive 2.27%/80% result. That advisory is distinct from the completed 120-file source review. This slice changes dashboard wording and matching test selectors. Adding bulk docstrings to existing functions would expand its scope without clarifying these changes; the repository has no corresponding required docstring coverage gate. I am declining that advisory. The actual lint, type, test and browser checks remain required on the final integrated head, and the source review's timed-out Greptile check context is covered separately by the completed fresh Greptile review. |
izadoesdev
force-pushed
the
codex/dashboard-copy
branch
from
October 6, 2026 07:22
fff667f to
04d0e32
Compare
Member
Author
|
Please re-review final head |
Member
Author
|
Unsupported change-descriptor concern disposition for The fresh Greptile summary asks to add two paths to a This appears to concern reviewer grouping metadata (an inference), rather than a product-source defect. I am declining an unsupported repository edit. Both paths and their reviewed diff are preserved; the final integrated head still requires fresh CI and review. |
…ashboard Sentence case for titles, buttons, menus, labels, and toasts; Create X / Save changes / Try again / Failed to load X; … instead of ...; no em dashes in prose; no 'successfully' or '!' in toasts; one badge variant per status. E2E selectors follow the new labels.
izadoesdev
force-pushed
the
codex/dashboard-copy
branch
from
October 6, 2026 07:40
04d0e32 to
c2d6213
Compare
Member
Author
|
Please re-review final head |
This branch was successfully deployed
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.
Standardize dashboard labels, errors, and empty states to sentence case and consistent action wording. Keep billing usage empty states neutral, and update the existing E2E selectors to match the visible copy.
The slice contains four coherent commits across 120 dashboard files. It is rebased onto current main, preserving merged stage badges, the updated Business context regression selectors, and the onboarding brief/setup improvements from #1087. No backend contracts, schemas, or tracker publication change.
Validation: touched-file format checks, root lint, root type checks, and 11 billing tests (46 assertions) pass. CI and both configured Dashboard Playwright suites must pass on the published final head before merge.
AI assistance: Codex reviewed and integrated the slice. No dependency on an unmerged PR.
Summary by CodeRabbit