HollowMan6 commented on issue #9697: URL: https://github.com/apache/shardingsphere/issues/9697#issuecomment-843155712
Hi! I'm a student from [Summer 2021](https://summer.iscas.ac.cn/#/org/orgdetail/apacheshardingsphere). I would like to do this project as the Summer 2021 Project. For automatically publish docs to shardingsphere-doc repository when released, I have a workflow which helps me automaticly sync repos from GitHub to Gitee: https://github.com/HollowMan6/LZU-Auto-COVID-Health-Report/blob/main/.github/workflows/repo-sync.yml , the mechanism behind this is such code: https://github.com/wearerequired/git-mirror-action/blob/master/git-mirror.sh . So I think such a logic can be used for realizing this feature, too. Just generate those docs then auto push commits to shardingsphere-doc repository. For automating the issue standard handling process, I guess a workflow may not be the best way? Why not try some bots in GitHub Apps for this, such as https://github.com/marketplace/issue-label-bot . If such kind of bot can't be found, I can also help to make one. I'm the author of the LZU COVID Health Report: https://github.com/marketplace/lzu-covid-health-report , which now ranks first in GitHub MarketPlace Trending.  For automatically publish image to docker registry when released, I actually have a project that has realized this feature to push image to docker hub and also GitHub Container Registry with multiple architecture support realized by docker buildx: every time when I push a new commit, the workflow will automatically push the image with tag `latest`, and when I release a version, the released version's image will be automatically pushed to the registry tagged correctly. The workflow also supports a manual dispatch specifying the tag.  Here's the link of my workflow file for automatically publish image to docker registry : https://github.com/HollowMan6/LZU-Auto-COVID-Health-Report/blob/main/.github/workflows/docker-publish.yml Please tell me if I got something wrong or there's a better idea. Thanks! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
