Add .github/workflow/mirror_to_gitee.yml

[tuoping]

I found the problem. I've been invoking action in my personal repository: github.com/tuoping/dpgen. So the ssh-private-key in organization deepmodeling cannot be visited. We have to test the action after PR.

[codecov-commenter]

Codecov Report

Merging #475 (f0ccfce) into devel (86afc5b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##            devel     #475   +/-   ##
=======================================
  Coverage   32.97%   32.97%           
=======================================
  Files          86       86           
  Lines       14736    14736           
=======================================
  Hits         4859     4859           
  Misses       9877     9877           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 86afc5b...f0ccfce. Read the comment docs.

[tuoping]

In addition, may I ask how did you enable to sync issue from gitee to github?

[njzjz]

In addition, may I ask how did you enable to sync issue from gitee to github?

A simple method... Set up this bot and then forward the Gitee notification emails to it. (Create a rule in Gmail)

[tuoping]

Sorry about that. But this action still failed with the same error message in my repository tuoping/dpgen. I still think the action need to be invoked in deepmodeling/dpgen.

[njzjz]

Did you set the secret in your own repo?

[tuoping]

The point of this is to test the secret in organization. That's not a bad idea though, to set the secret in my own repo and PR with the mirror_to_gitee.yml file. This way the secret in organization will be of no use.

[njzjz]

If you want to test the secret in organization, you need to push the branch into the organization repository. (or ask someone who has the access to help you)