Skip to content

Conversation

@shivangag
Copy link

@shivangag shivangag commented May 26, 2025

Related GitHub Issue

Closes: #

Description

Test Procedure

Type of Change

  • 🐛 Bug Fix: Non-breaking change that fixes an issue.
  • New Feature: Non-breaking change that adds functionality.
  • 💥 Breaking Change: Fix or feature that would cause existing functionality to not work as expected.
  • ♻️ Refactor: Code change that neither fixes a bug nor adds a feature.
  • 💅 Style: Changes that do not affect the meaning of the code (white-space, formatting, etc.).
  • 📚 Documentation: Updates to documentation files.
  • ⚙️ Build/CI: Changes to the build process or CI configuration.
  • 🧹 Chore: Other changes that don't modify src or test files.

Pre-Submission Checklist

  • Issue Linked: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
  • Scope: My changes are focused on the linked issue (one major feature/fix per PR).
  • Self-Review: I have performed a thorough self-review of my code.
  • Code Quality:
    • My code adheres to the project's style guidelines.
    • There are no new linting errors or warnings (npm run lint).
    • All debug code (e.g., console.log) has been removed.
  • Testing:
    • New and/or updated tests have been added to cover my changes.
    • All tests pass locally (npm test).
    • The application builds successfully with my changes.
  • Branch Hygiene: My branch is up-to-date (rebased) with the main branch.
  • Documentation Impact: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
  • Changeset: A changeset has been created using npm run changeset if this PR includes user-facing changes or dependency updates.
  • Contribution Guidelines: I have read and agree to the Contributor Guidelines.

Screenshots / Videos

Documentation Updates

Additional Notes

Get in Touch


Important

Renames project from 'Roo Cline' to 'Roo Otto', updates workflows, and modifies configurations in ClineProvider and package.json.

  • Renaming and Branding:
    • Rename project from Roo Cline to Roo Otto in package.json, constants.ts, and ClineProvider.ts.
    • Update DEFAULT_HEADERS in constants.ts to reflect new branding.
  • Workflow Changes:
    • Remove changeset-release.yml, discord-pr-notify.yml, and update-contributors.yml workflows.
    • Modify marketplace-publish.yml to trigger on publish label and update package paths.
  • Configuration and Settings:
    • Update ClineProvider to handle new settings and configurations, including allowedCommands and telemetry settings.
    • Set default allowedCommands to [*] in ClineProvider.ts.
  • Miscellaneous:
    • Update package.json with new publisher IdenWorks and repository URL.
    • Remove Korean and Chinese language files package.nls.ko.json and package.nls.zh-CN.json.

This description was created by Ellipsis for eca7393. You can customize this summary. It will automatically update as commits are pushed.

shivangag added 8 commits May 20, 2025 17:16
…ted configurations

- Updated package names and identifiers from "roo-cline" to "roo-otto" across all relevant files.
- Modified README and documentation links to reflect the new extension name.
- Removed outdated localization files and updated the main configuration to align with the new branding.
- Adjusted commands and API references to ensure compatibility with the new extension name.
refactor: rename extension from Roo Cline to Roo Otto and update rela…
publish extension on adding label 'publish'
…dentifiers in package.json, including publisher, author, repository URL, commands, and menus.
@shivangag shivangag requested review from cte and mrubens as code owners May 26, 2025 16:39
@shivangag shivangag closed this May 26, 2025
@github-project-automation github-project-automation bot moved this from New to Done in Roo Code Roadmap May 26, 2025
@github-project-automation github-project-automation bot moved this from New to Done in Roo Code Roadmap May 26, 2025
@shivangag shivangag deleted the upstream-merge branch May 26, 2025 16:39
@shivangag shivangag restored the upstream-merge branch May 26, 2025 16:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

1 participant