Skip to content

[docs] Fix broken Wuerstchen example links in zh training docs - #14394

Closed
richboyneedcash wants to merge 1 commit into
huggingface:mainfrom
richboyneedcash:fix-zh-wuerstchen-links
Closed

richboyneedcash wants to merge 1 commit into
huggingface:mainfrom
richboyneedcash:fix-zh-wuerstchen-links

Conversation

@richboyneedcash

Copy link
Copy Markdown

What does this PR do?

The Wuerstchen training example was moved from examples/wuerstchen/ to examples/research_projects/wuerstchen/. The Chinese training docs still link to the old main path, so those links 404.

This updates the 5 blob/main / tree/main links across:

  • docs/source/zh/training/overview.md
  • docs/source/zh/training/lora.md
  • docs/source/zh/training/wuerstchen.md

to the current examples/research_projects/wuerstchen/ location. Commit-pinned (SHA) links are intentionally left unchanged, since they correctly reference the file at that historical revision.

All updated targets were verified to exist on main. Docs-only change.

The Wuerstchen training example moved from examples/wuerstchen/ to
examples/research_projects/wuerstchen/, but the Chinese training docs
still link to the old path on main, so those links 404.

Update the 5 blob/main and tree/main links across overview.md, lora.md
and wuerstchen.md to the current research_projects/ path. Commit-pinned
(SHA) links are intentionally left unchanged since they reference the
historical file location.

Co-authored-by: TRAE CLI <noreply@bytedance.com>
@github-actions github-actions Bot added size/S PR with diff < 50 LOC documentation Improvements or additions to documentation labels Aug 5, 2026
@github-actions

github-actions Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Hi @richboyneedcash, thanks for the PR! It does not appear to link an issue it fixes. If this PR addresses an existing issue, please add a closing keyword (e.g. Fixes #1234) to the PR description so the issue is linked. See the contribution guide for more details. If this PR intentionally does not fix a tracked issue, a maintainer can add the no-issue-needed label to silence this reminder.

@github-actions

github-actions Bot commented Aug 22, 2026 •

Copy link
Copy Markdown
Contributor

Hi @richboyneedcash, a follow-up on the reminder above: this PR still does not link an issue it fixes.

Please note that PRs without a linked issue are likely to be automatically closed 10 days after this notice. Adding a closing keyword (e.g. Fixes #1234) to the PR description, or a maintainer adding the no-issue-needed label, will prevent that.

@sayakpaul
sayakpaul requested a review from stevhliu August 27, 2026 10:58

@stevhliu stevhliu left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

thanks for the fix!

@github-actions

github-actions Bot commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

This PR has been automatically closed because it does not link an issue and the reminder above was not addressed within 10 days. If this PR is still relevant, please link the issue it fixes (e.g. Fixes #1234) or ask a maintainer to add the no-issue-needed label, and it can be reopened.

We are experimenting with this process to keep the review queue manageable, and it will sometimes get it wrong. If you think this PR should stay open, please just say so here and we will reopen it — no need to justify it at length.

Thanks again for contributing, and sorry for the noise if we closed this by mistake!

@github-actions github-actions Bot closed this Sep 2, 2026
@stevhliu stevhliu reopened this Sep 2, 2026
@stevhliu

stevhliu commented Sep 2, 2026

Copy link
Copy Markdown
Member

hi, would you mind rebasing and then i can merge :)

@github-actions

github-actions Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

This PR has been automatically closed because it does not link an issue and the reminder above was not addressed within 10 days. If this PR is still relevant, please link the issue it fixes (e.g. Fixes #1234) or ask a maintainer to add the no-issue-needed label, and it can be reopened.

We are experimenting with this process to keep the review queue manageable, and it will sometimes get it wrong. If you think this PR should stay open, please just say so here and we will reopen it — no need to justify it at length.

Thanks again for contributing, and sorry for the noise if we closed this by mistake!

@github-actions github-actions Bot closed this Sep 3, 2026
@stevhliu stevhliu reopened this Sep 3, 2026
@github-actions

github-actions Bot commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

This PR has been automatically closed because it does not link an issue and the reminder above was not addressed within 10 days. If this PR is still relevant, please link the issue it fixes (e.g. Fixes #1234) or ask a maintainer to add the no-issue-needed label, and it can be reopened.

We are experimenting with this process to keep the review queue manageable, and it will sometimes get it wrong. If you think this PR should stay open, please just say so here and we will reopen it — no need to justify it at length.

Thanks again for contributing, and sorry for the noise if we closed this by mistake!

@github-actions github-actions Bot closed this Sep 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation size/S PR with diff < 50 LOC

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants