langgenius/dify-docs
1
0
Fork 0
mirror of https://github.com/langgenius/dify-docs.git synced 2026-07-22 04:15:24 -04:00
Code Issues 10 Packages Projects Releases Wiki Activity

[PR #432] [CLOSED] test: workflow translation test with new English documentation #500

New Issue
Closed
opened 2026-02-16 06:15:41 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 06:15:41 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-docs/pull/432
Author: @guchenhe
Created: 8/23/2025
Status: ❌ Closed

Base: revamp ← Head: test-workflow-translation-trigger

📝 Commits (1)

  • e9519b8 test: add workflow translation test documentation

📊 Changes

2 files changed (+78 additions, -0 deletions)

View changed files

📝 docs.json (+1 -0)
➕ en/documentation/pages/getting-started/workflow-test.mdx (+77 -0)

📄 Description

Test PR for Translation Workflow

This PR is created to test the automatic translation workflow. It contains:

  1. ✅ A new English documentation file: en/documentation/pages/getting-started/workflow-test.mdx
  2. ✅ Updated docs.json navigation structure (English section only)
  3. ❌ No translation files (Chinese or Japanese)

Expected Workflow Behavior

According to the workflow design:

  1. The Analyze Documentation Changes workflow should trigger on this PR
  2. It should categorize this as an English-only PR (not mixed content)
  3. The Execute Documentation Sync workflow should then:
    • Translate the new file to Chinese (zh-hans) and Japanese (ja-jp)
    • Update the navigation structure in docs.json for both languages
    • Create a separate translation PR with all generated translations

Testing Notes

  • This is a test PR to validate the workflow functionality
  • The new documentation page contains various markdown elements to test translation quality
  • The workflow should complete without manual intervention

Files Changed

  • en/documentation/pages/getting-started/workflow-test.mdx - New test documentation
  • docs.json - Added navigation entry for the test page

🧪 This is a test PR - please monitor the workflow execution

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langgenius/dify-docs/pull/432 **Author:** [@guchenhe](https://github.com/guchenhe) **Created:** 8/23/2025 **Status:** ❌ Closed **Base:** `revamp` ← **Head:** `test-workflow-translation-trigger` --- ### 📝 Commits (1) - [`e9519b8`](https://github.com/langgenius/dify-docs/commit/e9519b8ded13a9a159ac9b09b055b9fd5c03d1c8) test: add workflow translation test documentation ### 📊 Changes **2 files changed** (+78 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `docs.json` (+1 -0) ➕ `en/documentation/pages/getting-started/workflow-test.mdx` (+77 -0) </details> ### 📄 Description ## Test PR for Translation Workflow This PR is created to test the automatic translation workflow. It contains: 1. ✅ A new English documentation file: `en/documentation/pages/getting-started/workflow-test.mdx` 2. ✅ Updated `docs.json` navigation structure (English section only) 3. ❌ No translation files (Chinese or Japanese) ## Expected Workflow Behavior According to the workflow design: 1. The **Analyze Documentation Changes** workflow should trigger on this PR 2. It should categorize this as an **English-only PR** (not mixed content) 3. The **Execute Documentation Sync** workflow should then: - Translate the new file to Chinese (zh-hans) and Japanese (ja-jp) - Update the navigation structure in `docs.json` for both languages - Create a separate translation PR with all generated translations ## Testing Notes - This is a test PR to validate the workflow functionality - The new documentation page contains various markdown elements to test translation quality - The workflow should complete without manual intervention ## Files Changed - `en/documentation/pages/getting-started/workflow-test.mdx` - New test documentation - `docs.json` - Added navigation entry for the test page --- 🧪 **This is a test PR - please monitor the workflow execution** --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-16 06:15:41 -05:00
yindo closed this issue 2026-02-16 06:15:41 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
documentation
enhancement
pull-request
Mirrored from GitHub Pull Request
 question
stale
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-docs#500
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?