Purpose

This PR tend to automate several tasks with github action:

• Pulling latest source strings fromCPython daily and make the change as a PR (only support branch3.9).
  • Maintainer should resolve the fuzzy entries before merging it.
  • If the PR for this task is existed, changes will be forced-push to the existing branch (checkoutpeter-evans/create-pull-request@v3).
• Launch build flow during a pull request is opened (supported base branch:3.7,3.8, &3.9).
• Deploy to github page if any change is pushed to main branch (current:3.9).

Preview

These workflows are tested in my forked repo. One can check it out and learn how it works before merging this PR:

• Sync with CPython:
  • log of gh-action job
  • auto-generated PR
• Build:
  • example of a failed build (I deliberately make a rst syntax error inthis PR)
  • example of a success build
• Deploy to github page
  • log of gh-action job
  • resulting github page

Caution

• Need@adrianliaw's help to setup github page (configure branch asgh-pages and folder as root).
  
• To successfully deploy the site to github page, an empty file named.nojekyll is required to be committed togh-pages branch after this PR is merged. It prevents github page from ignoring folders that start with underscores, which makes it failed to load css/js files (seethis reference andthis blog for details).