Apex rebrand #3734
Closed
Apex rebrand #3734
Conversation
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
Fix typescript errors
Revert "Fix typescript errors"
- Added new SVG icon (iconn.svg) to assets/icons. - Updated panel_dark.png with new binary changes. - Modified chat.json to replace "Roo" with "Seawolf" in various strings for consistency. - Updated welcome.json to reflect the new branding and introduction message.
- Removed obsolete SVG icon file: assets/icons/iconn.svg - Updated panel_light.png with a new version - Replaced the existing roo-logo.svg with a new design - Changed author name from "Roo Code" to "Apex" in package.json - Updated various strings in chat.json to replace "Seawolf" with "Apex" - Modified welcome.json to reflect new branding for "Apex"
…Apex across multiple languages including Spanish, French, and Hindi. Changes include updates to greetings, descriptions, and settings to ensure consistency with the new branding.
…ew branding; correct base URL in docLinks utility
|
dosubot
bot
added
the
size:L
SmartManoj
pushed a commit
to SmartManoj/Raa-Code
that referenced
this pull request
Jun 13, 2025
* settings cancel * settings cancel --------- Co-authored-by: Cline Evaluation <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This pull request primarily focuses on rebranding the project from "Roo Code" to "Apex" across various files and configurations. Additionally, it includes minor adjustments to pre-commit and pre-push hooks and updates to
.roomodes. Below is a summary of the most important changes grouped by theme:Rebranding from "Roo Code" to "Apex":
bug_report.yml,feature_request.yml,config.yml) to reflect the new name "Apex" instead of "Roo Code." [1] [2] [3]pull_request_template.md) and GitHub Actions workflow for code quality (code-qa.yml). [1] [2].roomodesroles and instructions, including updates to role definitions and custom instructions for various modes. [1] [2] [3] [4]CHANGELOG.mdto replace all instances of "Roo Code" with "Apex" in headings, feature descriptions, and bug fix notes. [1] [2] [3] [4] [5] [6] [7] [8] [9]Pre-commit and Pre-push Hook Updates:
PATHenvironment variable adjustments to ensure compatibility with npm on Windows in.husky/pre-commitand.husky/pre-push. [1] [2]roo-code.d.tsafter runningnpm run generate-types.Important
Rebrands "Roo Code" to "Apex" across multiple files and updates pre-commit and pre-push hooks for better npm compatibility on Windows.
README.md,CONTRIBUTING.md,settings.json(bothcaanden), andTerminalRegistry.test.ts.docLinks.tsto usehttps://opensourceful.com.PATHadjustments for npm compatibility on Windows in.husky/pre-commitand.husky/pre-push.roo-code.d.tsafternpm run generate-types.This description was created by
for 2eacc16. You can customize this summary. It will automatically update as commits are pushed.