Fully translated in Georgian

[ZurabBalamtsarashvili]

Description

Added full Georgian language support to the project.

• Translated all JSON localization files (~2400 lines) into Georgian.
• Ensured consistent terminology and UI/UX phrasing.
• Verified proper encoding and rendering of Georgian characters across the interface.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• Feature (non-breaking change which adds functionality)
• Improvement (enhances existing functionality without breaking changes)
• Code refactoring
• Performance improvements
• Documentation update

Screenshots and Media (if applicable)

Add screenshots or recordings if needed to demonstrate Georgian UI rendering.

Test Scenarios

• Selected Georgian from language preferences and verified translations across the platform.
• Checked sidebar, projects, issues, settings, notifications, and other major modules.
• Confirmed special Georgian characters (e.g., „“, „ღ“, „შ“) display correctly.
• Verified fallback to English when translation is missing.

References

No related issues.

Summary by CodeRabbit

• New Features
  • Added Georgian (ka-GE) localization across core UI, including sidebar and authentication flows with pluralization and placeholders.
  • Introduced Georgian accessibility labels (ARIA) for project navigation and auth controls to improve screen reader support.
• Chores
  • Added placeholder Georgian locale stub for the editor module.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[coderabbitai]

Walkthrough

Adds Georgian (ka-ge) locale resources: accessibility ARIA labels, comprehensive core UI/auth translations, and an empty editor.json scaffold. No application logic or APIs changed.

Changes

Cohort / File(s)	Change Summary
Georgian locale additions packages/i18n/src/locales/ka-ge/.../accessibility.json, packages/i18n/src/locales/ka-ge/.../core.json, packages/i18n/src/locales/ka-ge/.../editor.json	Added ka-ge accessibility ARIA labels; added extensive core UI/auth translations; added empty editor.json placeholder. No code logic changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

I thump my paw in gleeful spree,
New words in ka-ge hop to me!
Aria whispers, auth will sing,
Core strings bloom with springtime zing.
Empty editor waits—tee-hee!
Translations planted, bun-approved 🌱🐇

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title "Fully translated in Georgian" accurately and concisely reflects the primary change — addition of Georgian locale files and extensive translations in the i18n package (ka-ge JSON files). It is a short, single-sentence summary that conveys the main intent to a reviewer scanning history. For minor grammatical clarity you could use "into Georgian," but the current title is clear and on-topic.
Description Check	✅ Passed	The PR description follows the repository template and includes a detailed Description of the changes, a populated Type of Change checklist, a Screenshots/media placeholder, Test Scenarios describing manual verification, and a References line, which satisfies the template requirements. It documents scope (~2400 lines), verification steps (language selection, rendering checks, fallback behavior), and the feature/improvement classification—covering the key information reviewers need. Minor optional items like attached screenshots or links to automated test/CI logs are not present but are not required for the description to be acceptable.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull Request Overview

This pull request adds complete Georgian language support by creating localization files for the ka-ge locale. The changes include translation of UI components, authentication flows, accessibility labels, and editor elements to Georgian.

Key changes:

• Added comprehensive Georgian translations for core UI elements (~170 translations)
• Implemented authentication flow translations including sign-up, sign-in, and password management
• Added accessibility labels for screen readers and assistive technology support

Reviewed Changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated 1 comment.

File	Description
packages/i18n/src/locales/ka-ge/editor.json	Creates empty editor translations file
packages/i18n/src/locales/ka-ge/core.json	Adds core UI translations including sidebar, authentication flows, and common elements
packages/i18n/src/locales/ka-ge/accessibility.json	Provides Georgian translations for accessibility labels and ARIA descriptions

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (3)

packages/i18n/src/locales/ka-ge/accessibility.json (1)

24-24: Double‑check “edition_badge” label intent.

“გადახდილი გეგმის ფანჯრის გახსნა” sounds like opening a window, while “badge” is a status/label. Please confirm the UX intent against the English source to avoid misleading screen‑reader output.

packages/i18n/src/locales/ka-ge/core.json (2)

141-141: Avoid leaking server config details in end‑user errors.

“Smtp_not_enabled” exposes internal state. Consider a neutral message while logging the diagnostic server‑side.

Suggested copy:

-        "smtp_not_enabled": "როგორც ვხედავთ, თქვენს სერვერზე SMTP არ არის ჩართული, ამიტომ პაროლის აღდგენის ბმულს ვერ გამოგიგზავნით"
+        "smtp_not_enabled": "ამ სერვერზე ელფოსტა ამჟამად მიუწვდომელია, ამიტომ პაროლის აღდგენის ბმულს ვერ გავგზავნით."

---

10-11: Minor terminology check for “views”.

Confirm “ხილვები” matches existing Georgian UX terminology for this section in Plane. If the product uses a different term elsewhere, align for consistency.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 47f68e3 and 685cfd5.

📒 Files selected for processing (3)

• packages/i18n/src/locales/ka-ge/accessibility.json (1 hunks)
• packages/i18n/src/locales/ka-ge/core.json (1 hunks)
• packages/i18n/src/locales/ka-ge/editor.json (1 hunks)

🔇 Additional comments (3)

packages/i18n/src/locales/ka-ge/accessibility.json (1)

1-34: Confirm locale casing aligns with project convention (BCP‑47).

Paths use ka-ge; many i18n setups expect region uppercase (ka-GE). Ensure the loader registers the exact variant you’re adding, or add an alias/mapping.

packages/i18n/src/locales/ka-ge/core.json (1)

88-89: Validate placeholder usage in resend text.

Ensure the runtime formatter expects {seconds} exactly (no “%s” or “{{}}”) and that countdown logic supplies an integer.

packages/i18n/src/locales/ka-ge/editor.json (1)

1-1: JSON & key parity OK — confirm locale registration and fallback.

• packages/i18n/src/locales/ka-ge/{core.json,accessibility.json,editor.json} validated: core/accessibility match en (no missing/extra); editor.json is empty ({}) and valid.
• Action: verify the i18n loader actually registers/loads "ka-ge" (e.g. packages/i18n/src/locales/index.ts or the loader entrypoint) so the editor UI falls back to the base locale for missing editor keys.

[pushya22]

#9720 here is the PR to provide full support for Georgian language on the platform.