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(tools): added apify block/tools (#2136)

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 Nov 30, 2025

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

Project Deployment Preview Comments Updated (UTC)
docs Ready Ready Preview Comment Nov 30, 2025 7:57am

@greptile-apps
Copy link
Contributor

greptile-apps bot commented Nov 30, 2025

Greptile Overview

Greptile Summary

Automated translation PR adding Apify tool documentation in 5 languages (Spanish, French, German, Japanese, Chinese).

  • Added translated versions of the Apify tool documentation across all supported languages
  • Updated i18n.lock with checksums for translation tracking
  • Japanese translation contains multiple "APIPY" typos that should be "APIFY"
  • Spanish translation has spacing issue: "nombreusuario" should be "nombre-usuario"
  • German, French, and Chinese translations appear accurate and well-formatted

Confidence Score: 3/5

  • This PR has translation errors that should be fixed before merging to ensure documentation quality
  • Multiple syntax errors in automated translations need correction - Japanese file has consistent "APIPY" typos (4 instances) and Spanish has spacing issues. These are straightforward fixes but important for documentation accuracy
  • Japanese translation (apps/docs/content/docs/ja/tools/apify.mdx) requires immediate attention for APIPY→APIFY corrections. Spanish translation needs minor spacing fix

Important Files Changed

File Analysis

Filename Score Overview
apps/docs/content/docs/de/tools/apify.mdx 5/5 New German translation for Apify tool documentation - translation appears accurate and well-formatted
apps/docs/content/docs/es/tools/apify.mdx 3/5 New Spanish translation with minor spacing issues in "nombreusuario" (should be "nombre-usuario")
apps/docs/content/docs/fr/tools/apify.mdx 5/5 New French translation - properly translated with correct technical terminology and formatting
apps/docs/content/docs/ja/tools/apify.mdx 2/5 New Japanese translation with multiple "APIPY" typos (should be "APIFY") in function descriptions and parameter tables
apps/docs/content/docs/zh/tools/apify.mdx 5/5 New Chinese translation - accurate translation with proper technical terminology and consistent formatting

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant GH as GitHub Actions
    participant Lingo as Lingo.dev AI
    participant Repo as Repository
    
    Dev->>Repo: Push commit (#2136: add Apify tools)
    Repo->>GH: Trigger translation workflow
    GH->>Lingo: Send English content for translation
    Lingo->>Lingo: Translate to ES, FR, DE, JA, ZH
    Lingo->>GH: Return translated files
    GH->>Repo: Create PR #2137 with translations
    GH->>Repo: Update i18n.lock checksums
    Note over Repo: PR ready 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, 6 comments

Edit Code Review Agent Settings | Greptile

| Parámetro | Tipo | Obligatorio | Descripción |
| --------- | ---- | ----------- | ----------- |
| `apiKey` | string | Sí | Token de API de APIFY desde console.apify.com/account#/integrations |
| `actorId` | string | Sí | ID del actor o nombreusuario/nombre-actor \(p.ej., "janedoe/my-actor" o ID del actor\) |
Copy link
Contributor

Choose a reason for hiding this comment

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

syntax: Missing space in translation - "nombreusuario" should be "nombre-usuario" or "nombre de usuario"

Suggested change
| `actorId` | string || ID del actor o nombreusuario/nombre-actor \(p.ej., "janedoe/my-actor" o ID del actor\) |
| `actorId` | string || ID del actor o nombre-usuario/nombre-actor \(p.ej., "janedoe/my-actor" o ID del actor\) |
Prompt To Fix With AI
This is a comment left during a code review.
Path: apps/docs/content/docs/es/tools/apify.mdx
Line: 45:45

Comment:
**syntax:** Missing space in translation - "nombreusuario" should be "nombre-usuario" or "nombre de usuario"

```suggestion
| `actorId` | string | Sí | ID del actor o nombre-usuario/nombre-actor \(p.ej., "janedoe/my-actor" o ID del actor\) |
```

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

| Parámetro | Tipo | Obligatorio | Descripción |
| --------- | ---- | ----------- | ----------- |
| `apiKey` | string | Sí | Token de API de APIFY desde console.apify.com/account#/integrations |
| `actorId` | string | Sí | ID del actor o nombreusuario/nombre-actor \(p.ej., "janedoe/my-actor" o ID del actor\) |
Copy link
Contributor

Choose a reason for hiding this comment

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

syntax: Same spacing issue - "nombreusuario" should be "nombre-usuario" or "nombre de usuario"

Suggested change
| `actorId` | string || ID del actor o nombreusuario/nombre-actor \(p.ej., "janedoe/my-actor" o ID del actor\) |
| `actorId` | string || ID del actor o nombre-usuario/nombre-actor \(p.ej., "janedoe/my-actor" o ID del actor\) |
Prompt To Fix With AI
This is a comment left during a code review.
Path: apps/docs/content/docs/es/tools/apify.mdx
Line: 69:69

Comment:
**syntax:** Same spacing issue - "nombreusuario" should be "nombre-usuario" or "nombre de usuario"

```suggestion
| `actorId` | string | Sí | ID del actor o nombre-usuario/nombre-actor \(p.ej., "janedoe/my-actor" o ID del actor\) |
```

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


### `apify_run_actor_sync`

APIPYアクターを同期的に実行して結果を取得(最大5分)
Copy link
Contributor

Choose a reason for hiding this comment

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

syntax: Typo - "APIPY" should be "APIFY"

Suggested change
APIPYアクターを同期的に実行して結果を取得(最大5分)
APIPYアクターを同期的に実行して結果を取得(最大5分)
Prompt To Fix With AI
This is a comment left during a code review.
Path: apps/docs/content/docs/ja/tools/apify.mdx
Line: 38:38

Comment:
**syntax:** Typo - "APIPY" should be "APIFY"

```suggestion
APIPYアクターを同期的に実行して結果を取得(最大5分)
```

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


| パラメータ | 型 | 必須 | 説明 |
| --------- | ---- | -------- | ----------- |
| `apiKey` | string | はい | console.apify.com/account#/integrationsから取得したAPIFY APIトークン |
Copy link
Contributor

Choose a reason for hiding this comment

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

syntax: Typo - "APIFY" is misspelled as "APIPY"

Suggested change
| `apiKey` | string | はい | console.apify.com/account#/integrationsから取得したAPIFY APIトークン |
| `apiKey` | string | はい | console.apify.com/account#/integrationsから取得したAPIPY APIトークン |
Prompt To Fix With AI
This is a comment left during a code review.
Path: apps/docs/content/docs/ja/tools/apify.mdx
Line: 44:44

Comment:
**syntax:** Typo - "APIFY" is misspelled as "APIPY"

```suggestion
| `apiKey` | string | はい | console.apify.com/account#/integrationsから取得したAPIPY APIトークン |
```

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


### `apify_run_actor_async`

長時間実行タスク用のポーリングを使用して、APIPYアクターを非同期で実行
Copy link
Contributor

Choose a reason for hiding this comment

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

syntax: Typo - "APIPY" should be "APIFY"

Suggested change
長時間実行タスク用のポーリングを使用して、APIPYアクターを非同期で実行
長時間実行タスク用のポーリングを使用して、APIPYアクターを非同期で実行
Prompt To Fix With AI
This is a comment left during a code review.
Path: apps/docs/content/docs/ja/tools/apify.mdx
Line: 62:62

Comment:
**syntax:** Typo - "APIPY" should be "APIFY"

```suggestion
長時間実行タスク用のポーリングを使用して、APIPYアクターを非同期で実行
```

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


| パラメータ | 型 | 必須 | 説明 |
| --------- | ---- | -------- | ----------- |
| `apiKey` | string | はい | console.apify.com/account#/integrationsから取得したAPIFY APIトークン |
Copy link
Contributor

Choose a reason for hiding this comment

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

syntax: Typo - "APIFY" is misspelled as "APIPY"

Suggested change
| `apiKey` | string | はい | console.apify.com/account#/integrationsから取得したAPIFY APIトークン |
| `apiKey` | string | はい | console.apify.com/account#/integrationsから取得したAPIPY APIトークン |
Prompt To Fix With AI
This is a comment left during a code review.
Path: apps/docs/content/docs/ja/tools/apify.mdx
Line: 68:68

Comment:
**syntax:** Typo - "APIFY" is misspelled as "APIPY"

```suggestion
| `apiKey` | string | はい | console.apify.com/account#/integrationsから取得したAPIPY APIトークン |
```

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

@waleedlatif1 waleedlatif1 merged commit f56d85b into staging Nov 30, 2025
9 checks passed
@waleedlatif1 waleedlatif1 deleted the auto-translate/staging-merge-19795780678 branch November 30, 2025 17:07
waleedlatif1 added a commit that referenced this pull request Dec 1, 2025
… sendgrid, linkedin, more tools (#2148)

* feat(tools): added smtp, sendgrid, mailgun, linkedin, fixed permissions in context menu (#2133)

* feat(tools): added twilio sendgrid integration

* feat(tools): added smtp, sendgrid, mailgun, fixed permissions in context menu

* added top level mocks for sporadically failing tests

* incr type safety

* fix(team-plans): track departed member usage so value not lost (#2118)

* fix(team-plans): track departed member usage so value not lost

* reset usage to 0 when they leave team

* prep merge with stagig

* regen migrations

* fix org invite + ws selection'

---------

Co-authored-by: Waleed <walif6@gmail.com>

* feat(i18n): update translations (#2134)

Co-authored-by: waleedlatif1 <waleedlatif1@users.noreply.github.com>

* feat(creators): add verification for creators (#2135)

* feat(tools): added apify block/tools  (#2136)

* feat(tools): added apify

* cleanup

* feat(i18n): update translations (#2137)

Co-authored-by: waleedlatif1 <waleedlatif1@users.noreply.github.com>

* feat(env): added more optional env var examples (#2138)

* feat(statuspage): added statuspage, updated list of tools in footer, renamed routes (#2139)

* feat(statuspage): added statuspage, updated list of tools in footer, renamed routes

* ack PR comments

* feat(tools): add generic search tool (#2140)

* feat(i18n): update translations (#2141)

* fix(sdks): bump sdk versions (#2142)

* fix(webhooks): count test webhooks towards usage limit (#2143)

* fix(bill): add requestId to webhook processing (#2144)

* improvement(subflow): remove all associated edges when moving a block into a subflow (#2145)

* improvement(subflow): remove all associated edges when moving a block into a subflow

* ack PR comments

* fix(polling): mark webhook failed on webhook trigger errors (#2146)

* fix(deps): declare core transient deps explicitly (#2147)

* fix(deps): declare core transient deps explicitly

* ack PR comments

---------

Co-authored-by: Vikhyath Mondreti <vikhyathvikku@gmail.com>
Co-authored-by: waleedlatif1 <waleedlatif1@users.noreply.github.com>
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