Tracking issue for merging dm and ticdc repos

[Rustin170506]

• How to cherry-pick the specific commit<COMMIT_SHA> to DM repo See: https://github.com/pingcap/ticdc/issues/3194#issuecomment-954837205
• Github Actions: https://github.com/pingcap/ticdc/issues/3173
• Merge the dm and cdc code into the root directory to make it conform to the go project standard structure ref: https://github.com/pingcap/ticdc/issues/2199
• https://github.com/pingcap/ticdc/issues/3175
• How to write the subsystem field in PR description, to distinguish whether the PR relates to DM or TiCDC #3195
• Refine required field in CI test. ref: config: update required status for TiCDC ti-community-infra/configs#453
• Refine CI trigger command, @hi-rustin will adjust it.
  • Add CI command description documentation #3196
• Reuse codes
  • https://github.com/pingcap/ticdc/issues/3242

[Rustin170506]

How to cherry-pick the specific commit<COMMIT_SHA> to DM repo?

• if the <COMMIT_SHA> not in <SPLIT_BRANCH>:
  • In TiCDC repo:
    • git subtree split --prefix=dm -b <SPLIT_BRANCH>
    • git checkout <SPLIT_BRANCH>
    • git push <DM_REPO_REMOTE>
    • <COMMIT_SHA>:refs/heads/<SPLIT_BRANCH>
• In DM repo:
  • git fetch origin <SPLIT_BRANCH>
  • git checkout master
  • git checkout -b <pick_from_ticdc>
  • git cherry-pick <COMMIT_SHA>
• Give a PR of merge <pick_from_ticdc> to master.

[sleepymole]

We also need to integrate the DM code structure into the root project structure, rather than always as a sub directory.

[Rustin170506]

We also need to integrate the DM code structure into the root project structure, rather than always as a sub directory.

Having adjusted the third TODO item description, we do need to work towards a standard structure!

[Ehco1996]

how about merge dm/pkg/xx to pkg/xx ?

[lonng]

how about merge dm/pkg/xx to pkg/xx ?

Make sense