Skip to content

docs: add Turkish translation for README#10552

Closed
EMREYSLCY wants to merge 1 commit into
NousResearch:mainfrom
EMREYSLCY:fix/json-parse-handling
Closed

docs: add Turkish translation for README#10552
EMREYSLCY wants to merge 1 commit into
NousResearch:mainfrom
EMREYSLCY:fix/json-parse-handling

Conversation

@EMREYSLCY
Copy link
Copy Markdown

What does this PR do?

Related Issue

Fixes #

Type of Change

  • 🐛 Bug fix (non-breaking change that fixes an issue)
  • ✨ New feature (non-breaking change that adds functionality)
  • 🔒 Security fix
  • 📝 Documentation update
  • ✅ Tests (adding or improving test coverage)
  • ♻️ Refactor (no behavior change)
  • 🎯 New skill (bundled or hub)

Changes Made

How to Test

Checklist

Code

  • I've read the Contributing Guide
  • My commit messages follow Conventional Commits (fix(scope):, feat(scope):, etc.)
  • I searched for existing PRs to make sure this isn't a duplicate
  • My PR contains only changes related to this fix/feature (no unrelated commits)
  • I've run pytest tests/ -q and all tests pass
  • I've added tests for my changes (required for bug fixes, strongly encouraged for features)
  • I've tested on my platform:

Documentation & Housekeeping

  • I've updated relevant documentation (README, docs/, docstrings) — or N/A
  • I've updated cli-config.yaml.example if I added/changed config keys — or N/A
  • I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — or N/A
  • I've considered cross-platform impact (Windows, macOS) per the compatibility guide — or N/A
  • I've updated tool descriptions/schemas if I changed tool behavior — or N/A

For New Skills

  • This skill is broadly useful to most users (if bundled) — see Contributing Guide
  • SKILL.md follows the standard format (frontmatter, trigger conditions, steps, pitfalls)
  • No external dependencies that aren't already available (prefer stdlib, curl, existing Hermes tools)
  • I've tested the skill end-to-end: hermes --toolsets skills -q "Use the X skill to do Y"

Screenshots / Logs

@alt-glitch alt-glitch added type/docs Documentation improvements P3 Low — cosmetic, nice to have labels Apr 25, 2026
@teknium1
Copy link
Copy Markdown
Contributor

teknium1 commented May 5, 2026

This README.tr.md is 13 lines and ends with "Projeyi bilgisayarınıza kurmak ve çalıştırmak için gereken tüm teknik adımlara ve komutlara orijinal README.md dosyasından ulaşabilirsiniz" (see the English README for install/usage steps), which isn't really a translation — it's more of a 3-paragraph summary. A useful translated README needs to mirror the full content (features, install, quickstart, configuration, etc.) the way the Chinese README (#20431 / README.zh-CN.md) does.

If you'd like to contribute a full Turkish translation matching the English README structure, we'd happily take that as a new PR. Closing this one for now, thanks @EMREYSLCY.

@teknium1 teknium1 closed this May 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

P3 Low — cosmetic, nice to have type/docs Documentation improvements

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants