Skip to content

Migrate Gitpod integration branding to Ona

Cornelius Ludmannrequested to merge
corneliusludmann/gitlab:migrate-gitpod-to-ona-branding into master

What does this MR do and why?

This MR migrates all user-facing references from "Gitpod" to "Ona" following the service rebrand, while maintaining complete backward compatibility. The changes focus exclusively on user-visible text and URLs to provide a clean, focused migration that can be safely deployed without breaking existing integrations.

Scope of this MR:

  • Updates default URL from https://gitpod.io/ to https://app.ona.com/
  • Replaces user-facing text "Gitpod" → "Ona" in UI components, admin settings, and user preferences
  • Updates documentation and API descriptions
  • Updates test files to match new branding expectations

Intentionally excluded from this MR (for future iterations):

  • Database schema changes (column renames would require migrations and downtime)
  • Internal method and file renames (would require coordinated updates across codebase)
  • API field name changes (would be breaking changes for external integrations)

This approach ensures zero breaking changes and zero downtime while delivering complete Ona branding to users.

References

Partially addresses #567831 - focuses on user-facing branding changes only. Additional MRs will be needed for internal naming consistency (database schema, method names, API fields) as outlined in the issue.

Screenshots or screen recordings

Examples:

Before After
Admin Settings: "Enable Gitpod integration" Admin Settings: "Enable Ona integration"
Merge Request: "Open in Gitpod" button Merge Request: "Open in Ona" button
User Preferences: "Gitpod" section User Preferences: "Ona" section

How to set up and validate locally

  1. Admin Settings Validation:

    1. Visit /admin/application_settings/general#js-gitpod-settings
2. Verify section title shows "Ona"
3. Verify form shows "Enable Ona integration"
4. Verify URL field shows "Ona URL" with placeholder "https://app.ona.com"

  2. User Preferences Validation:

    1. Visit /-/profile/preferences#integrations
2. Verify "Ona" section appears instead of "Gitpod"
3. Verify checkbox shows "Enable Ona integration"

  3. Merge Request Integration:

    1. Open any merge request
2. Click "Code" dropdown
3. Verify "Open in Ona" option appears (when integration is enabled)

  4. API Validation:

    1. Query GraphQL endpoint for gitpod_enabled field
2. Verify field descriptions reference "Ona" instead of "Gitpod"
3. Confirm field names remain unchanged for backward compatibility

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist.

Key considerations for this MR:

  • ✅ Zero breaking changes - All API fields and database columns unchanged
  • ✅ Zero downtime - No migrations or schema changes required
  • ✅ Backward compatibility - Existing integrations continue to work
  • ✅ Focused scope - Only user-facing text and URLs updated
  • ✅ Test coverage - All test files updated to match new expectations

Files changed: 34 files (UI components, documentation, configuration descriptions, test files)

Lines changed: 98 insertions, 98 deletions (net neutral)

Edited by Cornelius Ludmann

Merge request reports