Skip to content

Conversation

@waleedlatif1
Copy link
Collaborator

Summary

Automated translation updates triggered by changes to documentation.

This PR was automatically created after content changes were made, updating translations for all supported languages using Lingo.dev AI translation engine.

Original trigger: feat(schedules): remove save button for schedules, couple schedule deployment with workflow deployment (#2566)

Type of Change

  • Bug fix
  • New feature
  • Breaking change
  • Documentation
  • Other: ___________

Testing

This PR includes automated translations for modified English documentation content:

  • 🇪🇸 Spanish (es) translations
  • 🇫🇷 French (fr) translations
  • 🇨🇳 Chinese (zh) translations
  • 🇯🇵 Japanese (ja) translations
  • 🇩🇪 German (de) translations

What reviewers should focus on:

  • Verify translated content accuracy and context
  • Check that all links and references work correctly in translated versions
  • Ensure formatting, code blocks, and structure are preserved
  • Validate that technical terms are appropriately translated

Checklist

  • Code follows project style guidelines (automated translation)
  • Self-reviewed my changes (automated process)
  • Tests added/updated and passing
  • No new warnings introduced
  • I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

Screenshots/Videos

@vercel
Copy link

vercel bot commented Dec 24, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
docs Ready Ready Preview, Comment Dec 24, 2025 3:04am

@waleedlatif1 waleedlatif1 merged commit 3a50ce4 into staging Dec 24, 2025
6 of 7 checks passed
@greptile-apps
Copy link
Contributor

greptile-apps bot commented Dec 24, 2025

Greptile Summary

Automated translation updates for schedule trigger documentation across five languages (German, Spanish, French, Japanese, and Chinese).

Key Changes:

  • Removed unused Video component import from all translation files
  • Updated schedule activation behavior to reflect deployment coupling
  • Changed automatic disabling threshold from 3 to 10 consecutive failures
  • Simplified schedule configuration instructions
  • Updated terminology from "workflow triggers" to "workflow entry points"

Translation Quality:
The translations accurately reflect the English source content with appropriate localization. All technical terms (cron, workflow, schedule) are handled consistently. Formatting, code blocks, and component syntax are preserved correctly across all languages.

Confidence Score: 4/5

  • This PR is safe to merge with one minor translation inconsistency
  • Automated translation system produced high-quality, consistent translations across all languages. One issue found: Japanese translation has untranslated tab labels. All other translations maintain proper formatting, preserve code blocks, and accurately convey the English content
  • Pay attention to apps/docs/content/docs/ja/triggers/schedule.mdx - tab labels need translation

Important Files Changed

Filename Overview
apps/docs/content/docs/de/triggers/schedule.mdx German translation updated correctly, removed Video import, updated schedule activation and failure handling content
apps/docs/content/docs/es/triggers/schedule.mdx Spanish translation updated correctly, removed Video import, updated schedule activation and failure handling content
apps/docs/content/docs/fr/triggers/schedule.mdx French translation updated correctly, removed Video import, updated schedule activation and failure handling content
apps/docs/content/docs/ja/triggers/schedule.mdx Japanese translation updated but Tabs items attribute not translated (left in English)
apps/docs/content/docs/zh/triggers/schedule.mdx Chinese translation updated correctly, removed Video import, updated schedule activation and failure handling content

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant GH as GitHub Actions
    participant Lingo as Lingo.dev AI
    participant Docs as Documentation Files
    
    Dev->>GH: Merge PR #2566 (schedule feature changes)
    GH->>GH: Detect changes to English docs
    GH->>Lingo: Trigger translation workflow
    Lingo->>Docs: Read English source (schedule.mdx)
    Lingo->>Lingo: Translate to 5 languages (de, es, fr, ja, zh)
    Lingo->>Docs: Update German translation
    Lingo->>Docs: Update Spanish translation
    Lingo->>Docs: Update French translation
    Lingo->>Docs: Update Japanese translation
    Lingo->>Docs: Update Chinese translation
    Lingo->>Docs: Update i18n.lock checksums
    Lingo->>GH: Create PR #2568 with translations
    GH->>Dev: Notify for review
Loading

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

5 files reviewed, 1 comment

Edit Code Review Agent Settings | Greptile

ワークフローの実行タイミングを設定します

<Tabs items={['簡単な間隔', 'Cron式']}>
<Tabs items={['Simple Intervals', 'Cron Expressions']}>
Copy link
Contributor

Choose a reason for hiding this comment

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

syntax: tab labels not translated in Japanese

the items array for Tabs should be in Japanese to match the rest of the document

Suggested change
<Tabs items={['Simple Intervals', 'Cron Expressions']}>
<Tabs items={['簡単な間隔', 'Cron式']}>
Prompt To Fix With AI
This is a comment left during a code review.
Path: apps/docs/content/docs/ja/triggers/schedule.mdx
Line: 25:25

Comment:
**syntax:** tab labels not translated in Japanese

the `items` array for Tabs should be in Japanese to match the rest of the document

```suggestion
<Tabs items={['簡単な間隔', 'Cron式']}>
```

How can I resolve this? If you propose a fix, please make it concise.

@waleedlatif1 waleedlatif1 deleted the auto-translate/staging-merge-20476884644 branch December 24, 2025 18:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants