docs(readme): add Translations section listing the Turkish adaptation#159
Open
fatihguner wants to merge 1 commit into
Open
docs(readme): add Translations section listing the Turkish adaptation#159fatihguner wants to merge 1 commit into
fatihguner wants to merge 1 commit into
Conversation
FORKING.md's "For Other Languages" section asks language-variant forks to "Submit a PR to link your fork from the main README". This adds a Translations section between Contributing and Sponsor the work and lists the first community translation: - 🇹🇷 Turkish: https://github.com/komunite/ai-engineering maintained by Komünite (https://komunite.com.tr) live site: https://ai-muhendisligi.komunite.com.tr The Turkish adaptation tracks this upstream as canonical and ships every lesson translated. Future translations into other languages can append to the same section, keeping discoverability in one place. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
📝 WalkthroughWalkthroughThis PR adds a new "Translations" section to README.md that documents community-maintained language adaptations. The section includes a Turkish translation entry with its GitHub repository link, maintainer attribution, and corresponding site URL. ChangesTranslation Documentation
🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@README.md`:
- Around line 1051-1053: The decorative unlabeled fenced code block that
triggers markdownlint rule MD040 should be replaced with a non-fenced separator:
remove the triple-backtick fenced block containing the decorative line (the line
starting with the repeated "░░░▒▒▒..." pattern) and instead wrap that decorative
line between Markdown horizontal rules (e.g., --- above and --- below) so it is
not treated as a code fence.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
Comment on lines
+1051
to
+1053
| ``` | ||
| ░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒ | ||
| ``` |
There was a problem hiding this comment.
Replace unlabeled fenced block to satisfy markdownlint.
At Line 1051, the decorative fence triggers MD040 (missing fenced-code language). Use a non-fenced separator instead.
Suggested fix
-```
-░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒
-```
+---
+░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒
+---📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| ``` | |
| ░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒ | |
| ``` | |
| --- | |
| ░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒░░░▒▒▒ | |
| --- |
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 1051-1051: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@README.md` around lines 1051 - 1053, The decorative unlabeled fenced code
block that triggers markdownlint rule MD040 should be replaced with a non-fenced
separator: remove the triple-backtick fenced block containing the decorative
line (the line starting with the repeated "░░░▒▒▒..." pattern) and instead wrap
that decorative line between Markdown horizontal rules (e.g., --- above and ---
below) so it is not treated as a code fence.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Per
FORKING.md→ For Other Languages (step 4 — "Submit a PR to link your fork from the main README"), this PR adds a## Translationssection between Contributing and Sponsor the work and lists the first community translation:The Turkish adaptation:
.tr.md/.tr.jsonsiblings + Turkish-canonical site/build)ai-muhendisligi.komunite.com.trwith proper SEO (per-lesson OG, JSON-LDCourse/LearningResource/BreadcrumbList,llms.txt, sitemap, etc.)The new section also includes a one-line invitation for future translation maintainers to PR themselves in, so this stays self-extending.
Test plan
##) matches the surrounding heading depth🤖 Generated with Claude Code