doc: translation for docs/tutorials/timeseriees-forecasting-by-dsp.md

[jxs1211]

Signed-off-by: shenxianjie [email protected]

What type of PR is this?

translate docs/tutorials/timeseriees-forecasting-by-dsp.md

What this PR does / why we need it:

fix the issue #421

Which issue(s) this PR fixes:

Fixes #421

[github-actions[bot]]

🎊 PR Preview 9f744a4c4d92f5bafe13ed2065a1bfafa53de13f has been successfully built and deployed to https://gocrane-crane-preview-pr-451.surge.sh

:clock1: Build time: 5.358s

_{🤖 By surge-preview}

[zsnmwy]

Thanks for your pull request. :)

[jxs1211]

Thanks for your pull request. :)

@zsnmwy I have fixed all the comments. There is a problem here, I firstly commit the pr on a computer, but now I notice I can't get the content of my first commit when I am using another computer after pulling the forked repo. I found out the commit's SHA and attach to it, then the first commit come back,

[going@dev crane]$ git branch
* (HEAD detached from f33e209)
  main

so I fixed and update the tag, Now I have no idea how to push the pr in the right way, I try to push it as below:

origin  [email protected]:jxs1211/crane.git (fetch)
origin  [email protected]:jxs1211/crane.git (push)
upstream        [email protected]:gocrane/crane.git (fetch)
upstream        no_push (push)
[going@dev crane]$ git push origin f33e209:main

but it seems don't trigger the ci. Could you do me a favor to resolve the situation?

[qmhu]

Thanks for your pull request. :)

@zsnmwy I have fixed all the comments. There is a problem here, I firstly commit the pr on a computer, but now I notice I can't get the content of my first commit when I am using another computer after pulling the forked repo. I found out the commit's SHA and attach to it, then the first commit come back,

[going@dev crane]$ git branch
* (HEAD detached from f33e209)
  main

so I fixed and update the tag, Now I have no idea how to push the pr in the right way, I try to push it as below:

origin  [email protected]:jxs1211/crane.git (fetch)
origin  [email protected]:jxs1211/crane.git (push)
upstream        [email protected]:gocrane/crane.git (fetch)
upstream        no_push (push)
[going@dev crane]$ git push origin f33e209:main

but it seems don't trigger the ci. Could you do me a favor to resolve the situation?

如果弄混了，可以这样： 重新clone一个文件夹，checkout到你的branch，本地准备好你的提交内容，git commit，git push -f origin {your-branch}

[jxs1211]

Thanks for your pull request. :)

@zsnmwy I have fixed all the comments. There is a problem here, I firstly commit the pr on a computer, but now I notice I can't get the content of my first commit when I am using another computer after pulling the forked repo. I found out the commit's SHA and attach to it, then the first commit come back,

[going@dev crane]$ git branch
* (HEAD detached from f33e209)
  main

so I fixed and update the tag, Now I have no idea how to push the pr in the right way, I try to push it as below:

origin  [email protected]:jxs1211/crane.git (fetch)
origin  [email protected]:jxs1211/crane.git (push)
upstream        [email protected]:gocrane/crane.git (fetch)
upstream        no_push (push)
[going@dev crane]$ git push origin f33e209:main

but it seems don't trigger the ci. Could you do me a favor to resolve the situation?

如果弄混了，可以这样： 重新clone一个文件夹，checkout到你的branch，本地准备好你的提交内容，git commit，git push -f origin {your-branch}

@zsnmwy @qmhu I've opened another pr#452 for this issue, please close this pr.

[zsnmwy]

Thanks for your pull request. :)

@zsnmwy I have fixed all the comments. There is a problem here, I firstly commit the pr on a computer, but now I notice I can't get the content of my first commit when I am using another computer after pulling the forked repo. I found out the commit's SHA and attach to it, then the first commit come back,

[going@dev crane]$ git branch
* (HEAD detached from f33e209)
  main

so I fixed and update the tag, Now I have no idea how to push the pr in the right way, I try to push it as below:

origin  [email protected]:jxs1211/crane.git (fetch)
origin  [email protected]:jxs1211/crane.git (push)
upstream        [email protected]:gocrane/crane.git (fetch)
upstream        no_push (push)
[going@dev crane]$ git push origin f33e209:main

but it seems don't trigger the ci. Could you do me a favor to resolve the situation?

如果弄混了，可以这样： 重新clone一个文件夹，checkout到你的branch，本地准备好你的提交内容，git commit，git push -f origin {your-branch}

@zsnmwy @qmhu I've opened another pr#452 for this issue, please close this pr.

Not the same content with #451 and #452. Is right?

[zsnmwy]

Thanks for your pull request. :)

@zsnmwy I have fixed all the comments. There is a problem here, I firstly commit the pr on a computer, but now I notice I can't get the content of my first commit when I am using another computer after pulling the forked repo. I found out the commit's SHA and attach to it, then the first commit come back,

[going@dev crane]$ git branch
* (HEAD detached from f33e209)
  main

so I fixed and update the tag, Now I have no idea how to push the pr in the right way, I try to push it as below:

origin  [email protected]:jxs1211/crane.git (fetch)
origin  [email protected]:jxs1211/crane.git (push)
upstream        [email protected]:gocrane/crane.git (fetch)
upstream        no_push (push)
[going@dev crane]$ git push origin f33e209:main

but it seems don't trigger the ci. Could you do me a favor to resolve the situation?

The commit f33e209 is already pushed to jxs1211/crane:main. Nothing will be changed if you try to push the same commit twice because the commit is already in GitHub. Push the same commit can't trigger the CI.

1. You can use the git stash to save your work - docs fix.
2. Use Github official CLI to get the pr content. gh pr checkout 451. The CLI just wrapper git command.
3. Use git stash pop to recover your work.
4. Follow the after guide.

Ref: git stash

---

If you want to make some content changes, I recommend the two methods.

• standard dev.

  git checkout jxs1211/doc-translation-timeseriees-forecasting-by-dsp
  echo "A" >> test.md
  git add .
  git commit -m "Add A" -s
  git push
  

• Changing the Last Commit with amend

  git checkout jxs1211/doc-translation-timeseriees-forecasting-by-dsp
  # Edit hello.py and main.py
  git add hello.py
  git commit # Here, maybe get the commit SHA - 123123. 
  git push # Now you can see the commit hash - 123123 on the Github page.
  # Realize you forgot to add the changes from main.py or want to fix some problems.
  git add main.py 
  git commit --amend --no-edit # Here, maybe get the commit SHA - 456456
  # Notice the git history is changed. You must use the `--force` params when using git push. Replace the remote git history with the local git history. You must ensure the remote repo history no one use or changes.
  git push --force # Now you can see the new commit hash - 456456 on the Github page. The remote git history will miss the hash 123123.
  

  You must ensure the remote repo history no one use or changes. You must ensure the remote repo history no one use or changes. You must ensure the remote repo history no one use or changes.

Ref: git amend

[jxs1211]

Thanks for your pull request. :)

@zsnmwy I have fixed all the comments. There is a problem here, I firstly commit the pr on a computer, but now I notice I can't get the content of my first commit when I am using another computer after pulling the forked repo. I found out the commit's SHA and attach to it, then the first commit come back,

[going@dev crane]$ git branch
* (HEAD detached from f33e209)
  main

so I fixed and update the tag, Now I have no idea how to push the pr in the right way, I try to push it as below:

origin  [email protected]:jxs1211/crane.git (fetch)
origin  [email protected]:jxs1211/crane.git (push)
upstream        [email protected]:gocrane/crane.git (fetch)
upstream        no_push (push)
[going@dev crane]$ git push origin f33e209:main

but it seems don't trigger the ci. Could you do me a favor to resolve the situation?

The commit f33e209 is already pushed to jxs1211/crane:main. Nothing will be changed if you try to push the same commit twice because the commit is already in GitHub. Push the same commit can't trigger the CI.

1. You can use the git stash to save your work - docs fix.
2. Use Github official CLI to get the pr content. gh pr checkout 451. The CLI just wrapper git command.
3. Use git stash pop to recover your work.
4. Follow the after guide.

Ref: git stash

If you want to make some content changes, I recommend the two methods.

• standard dev.

  git checkout jxs1211/doc-translation-timeseriees-forecasting-by-dsp
  echo "A" >> test.md
  git add .
  git commit -m "Add A" -s
  git push
  

• Changing the Last Commit with amend

  git checkout jxs1211/doc-translation-timeseriees-forecasting-by-dsp
  # Edit hello.py and main.py
  git add hello.py
  git commit # Here, maybe get the commit SHA - 123123. 
  git push # Now you can see the commit hash - 123123 on the Github page.
  # Realize you forgot to add the changes from main.py or want to fix some problems.
  git add main.py 
  git commit --amend --no-edit # Here, maybe get the commit SHA - 456456
  # Notice the git history is changed. You must use the `--force` params when using git push. Replace the remote git history with the local git history. You must ensure the remote repo history no one use or changes.
  git push --force # Now you can see the new commit hash - 456456 on the Github page. The remote git history will miss the hash 123123.
  

  You must ensure the remote repo history no one use or changes. You must ensure the remote repo history no one use or changes. You must ensure the remote repo history no one use or changes.

Ref: git amend

@zsnmwy I try my best to fix all the comments, the push problem has been resolved, tks for your advice and patient reply, hope this time won't miss anything.