Automatically update and publish to GitHub pages using GitHub actions

[BlueHtml]

Hello, I have upgraded uglify-es to uglify-js, and added the feature of using GitHub actions to automatically update and publish to GitHub pages.

Here are the specific changes:

• Add GitHub actions to publish on GitHub pages;
• Change uglify-es to uglify-js;
• When building, download uglify-js from GitHub releases instead of git;
• When publishing, use CDN(registry.npmmirror.com) instead of local files for uglify-js;

Update steps:

1. On the GitHub actions page, manually run workflow update to build and publish to the gh-pages branch;
2. Let GitHub pages use gh-pages branch;

[Skalman]

@BlueHtml, thank you, I really appreciate the PR!

[Skalman]

Thanks for helping to modernize this repo using GH actions. Just a couple of minor suggestions for how to avoid unnecessary dependencies.

[Skalman]

What advantages are there to using this custom action instead of Github's "standard" actions? I'm not familiar with either, so I was just looking at Github's suggested workflows, in this case the "static HTML" one.

# Github's suggestion: "Static HTML"
      - name: Setup Pages
        uses: actions/configure-pages@v5
      - name: Upload artifact
        uses: actions/upload-pages-artifact@v3
        with:
          # Upload entire repository
          path: '.'
      - name: Deploy to GitHub Pages
        id: deployment
        uses: actions/deploy-pages@v4

[BlueHtml]

According to the GitHub Pages documentation:

Most external CI workflows "deploy" to GitHub Pages by committing the build output to the gh-pages branch of the repository, and typically include a .nojekyll file.

Use the actions/upload-pages-artifact action to upload the static files as an artifact.
use the actions/deploy-pages action to deploy the artifact.

• peaceiris/actions-gh-pages: This action creates a gh-pages branch, and we need to configure GitHub Pages to use this gh-pages branch.
  • Settings -> Pages -> Build and deployment -> Source -> Select Deploy from a branch -> Select gh-pages branch
• Github's "standard" actions (actions/upload-pages-artifact + actions/deploy-pages): This action will create an artifact, and then we need to configure GitHub Pages to use GitHub Actions.
  • Settings -> Pages -> Build and deployment -> Source -> Select GitHub Actions

I think using the gh-pages branch is better because switching branches allows you to see the generated static files.
But the artifact needs to be downloaded to view the file, and the artifact will expire, with a default of 90 days(By default, GitHub stores build logs and artifacts for 90 days, and this retention period can be customized.)

[Skalman]

Makes sense, thanks for explaining!

[Skalman]

I don't see the point of using a CDN here. We should be able to just copy the uglify dir into public, right?

[BlueHtml]

Certainly. I will remove CDN and use local files ( I am in China, CDN speed will be faster )

[Skalman]

Thanks. If we want to speed things up, it might help to concat the relevant JS files, but that could be done in a follow-up PR if you'd like.