fix(web): use "branch" wording in Git quick action copy#2525
fix(web): use "branch" wording in Git quick action copy#2525imabdulazeez wants to merge 2 commits into
Conversation
- Update dialog titles and descriptions to use "branch" - Clarify progress messages: "feature ref" → "feature branch" - Update error messages and hints for consistency - Change test expectations to match new terminology
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. 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 |
ApprovabilityVerdict: Approved Purely cosmetic copy changes replacing 'ref'/'refName' with 'branch' in user-facing strings. No logic or runtime behavior changes - just text updates and corresponding test adjustments. You can customize Macroscope's approvability policy. Learn more. |
|
CI failed |
|
fine for now since the component is still called git but this is probably a regression of introducing the more genercl vcs service in preparation for supporting other vcs systems like JJ (#2461) in the future, but we can tackle that when we get there |
Dismissing prior approval to re-evaluate 9a7fedc
There was a problem hiding this comment.
Sorry. This is embarassing. Had a edited version of Agents/Claude in a local branch and something must have got messed up here.. Closing this PR for now since its not a priority..
What changed
Cleaned up a few Git action labels that were showing
refName/refinstead ofbranch.Why
refNameseems like just an internal name. In the UI,branchis clearer. (And was the case in an old updateScreenshots
Before
After
Checklist
Note
Replace 'ref' with 'branch' in Git quick action UI copy
Updates user-facing strings in the Git actions control to use 'branch' terminology consistently instead of 'ref' or 'refName'. Affected surfaces include progress stage labels, disabled-reason messages, detached HEAD warnings, default-branch confirmation dialogs, and action button labels.
Macroscope summarized 9a7fedc.