dm: fix operate-source create description to match its actual behavior

[yahonda]

What is changed, added or deleted? (Required)

The usage example said "Use the following `operate-source` command to create a source configuration file", which describes the command backwards. The same document's own "Flags description" section (directly above) already states that `create` "Creates one or more upstream database sources" and that `config-file` "Specifies the file path of `source.yaml`" (an existing, pre-created input file) — i.e. the command registers an existing source file's contents into the DM cluster; it does not create the file.

Playground verification: deployed a live DM cluster (dm-master + dm-worker + dmctl v8.5.3) in a local Docker container and ran `operate-source create ./source.yaml`. No new file was written to disk, and `operate-source show` continued to report the source as registered even after `source.yaml` was deleted — confirming the command registers the source into cluster state rather than creating a file.

Source-code verification: `dm/ctl/master/operate_source.go` (`operateSourceFunc`) calls `common.GetFileContent(arg)` to read the existing `source.yaml`'s bytes, parses it with `config.SourceCfgFromYaml`, and sends the content over gRPC as `OperateSourceRequest{Config: contents, ...}`. The CLI never writes a file — it only reads one and transmits its content to dm-master.

Which TiDB version(s) do your changes apply to? (Required)

• master (the latest development version)
• v8.5 (TiDB 8.5 versions)
• v8.4 (TiDB 8.4 versions)
• v8.3 (TiDB 8.3 versions)
• v8.2 (TiDB 8.2 versions)
• v8.1 (TiDB 8.1 versions)
• v7.5 (TiDB 7.5 versions)
• v7.1 (TiDB 7.1 versions)
• v6.5 (TiDB 6.5 versions)

What is the related PR or file link(s)?

• This PR is translated from:
• Other reference link(s):

AI agent involvement

• The changes in this PR were primarily made by an AI agent on behalf of the PR author.

Do your changes match any of the following descriptions?

• Delete files
• Change aliases
• Need modification after applied to another branch
• Might cause conflicts after applied to another branch

Summary by CodeRabbit

• Documentation
  • Refined the usage example for the operate-source command to refer to creating a data source.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign lilin90 for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Advanced

Run ID: e0209e4b-9752-4dcf-893a-da20c44fd985

📥 Commits

Reviewing files that changed from the base of the PR and between 9c5b903 and 17c7076.

📒 Files selected for processing (1)

• dm/dm-manage-source.md

Included review availability: Your plan provides up to 4 included reviews per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The documentation updates the operate-source usage example to say “create a data source” instead of “create a source configuration file”. No functional behavior changes.

Changes

Documentation update

Layer / File(s)	Summary
Update source terminology dm/dm-manage-source.md	The operate-source usage example now uses “create a data source”.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~2 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 17c70

This documentation-only update does not affect runtime behavior and is safe to merge.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description explains the documentation change, provides verification details, identifies the applicable TiDB version, and includes the AI involvement and change-category sections. Optional referen…
Title check	✅ Passed	The title clearly describes the documentation fix for the operate-source create command and matches the main change.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}