Skip to content

chore: rename public-facing ORA branding to YonerAI - #111

Open
YoneRai12 wants to merge 1 commit into
mainfrom
codex/public-ora-branding-cleanup
Open

chore: rename public-facing ORA branding to YonerAI#111
YoneRai12 wants to merge 1 commit into
mainfrom
codex/public-ora-branding-cleanup

Conversation

@YoneRai12

Copy link
Copy Markdown
Owner

Summary

  • replace public-facing ORA branding with YonerAI across web UI, workflow names, and exposed Core titles
  • keep internal identifiers like ora_core and ORA_* env vars unchanged
  • remove lingering 'formerly ORA' wording from public system prompts

Testing

  • python -m pytest -q tests/test_settings_api.py tests/test_core_effective_route.py

Notes

  • excludes unrelated clients/web/package-lock.json worktree change
  • brand-only cleanup; no runtime contract changes

@gemini-code-assist

Copy link
Copy Markdown

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on a significant branding update, transitioning all public-facing mentions of 'ORA' to 'YonerAI'. The changes are purely cosmetic and do not introduce any functional modifications or runtime contract alterations, ensuring a seamless rebrand without impacting core system operations. The update aims to align the user experience with the new brand identity.

Highlights

  • Branding Renaming: The public-facing branding of 'ORA' has been comprehensively replaced with 'YonerAI' across various user interface elements, workflow names, and exposed Core titles.
  • Internal Identifiers Unchanged: Internal identifiers, such as 'ora_core' and 'ORA_*' environment variables, have been intentionally preserved to avoid breaking existing configurations or internal logic.
  • System Prompt Refinement: Lingering 'formerly ORA' wording has been removed from public system prompts to ensure consistent and current branding.
Changelog
  • .env.example
    • Updated the bot configuration comment from 'ORA Bot Configuration' to 'YonerAI Bot Configuration'.
  • clients/web/app/components/DashboardView.tsx
    • Changed the dashboard title from 'ORA Core' to 'YonerAI Core'.
  • clients/web/app/layout.tsx
    • Updated the HTML page title from 'ORA Chat' to 'YonerAI Chat'.
  • clients/web/app/page.tsx
    • Modified the error message for connection failures from 'ORA Brain' to 'YonerAI Brain'.
    • Updated the model selector text from 'ORA Model' to 'YonerAI Model'.
    • Changed the chat input placeholder text from 'Message ORA...' to 'Message YonerAI...'.
    • Revised the disclaimer text from 'ORA can make mistakes.' to 'YonerAI can make mistakes.'.
  • config.yaml
    • Updated the configuration file comment from 'ORA Bot Configuration' to 'YonerAI Bot Configuration'.
  • core/src/ora_core/brain/context.py
    • Removed '(formerly ORA)' from the system prompt that defines the AI assistant's identity.
  • core/src/ora_core/engine/simple_worker.py
    • Removed '(formerly ORA)' from the system prompt used in the mock stream dispatch.
    • Updated the default 'used_model' from 'ORA Universal Brain' to 'YonerAI Universal Brain'.
  • core/src/ora_core/main.py
    • Changed the FastAPI application title from 'ORA Core' to 'YonerAI Core'.
Ignored Files
  • Ignored by pattern: .github/workflows/** (2)
    • .github/workflows/core_test.yml
    • .github/workflows/test.yml
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the public-facing branding from "ORA" to "YonerAI". The changes are applied consistently across the web UI, configuration files, and internal system prompts. Internal identifiers and environment variables starting with ORA_ are correctly left unchanged as per the PR's scope. The removal of "(formerly ORA)" from prompts is also included. The submitted changes correctly implement the rebranding task.

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