Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.github/actions/deploy-to-github-pages: use Cloudflare API directly #1896

Merged
merged 1 commit into from
Oct 6, 2024

Commits on Oct 4, 2024

  1. .github/actions/deploy-to-github-pages: use Cloudflare API directly

    As pointed out in [1], using the cloudflare-purge-action incurs a ~31
    second penalty at the start of the "deploy" action, where time is spent
    building a Docker container to run the action.
    
    This is unnecessary, since Cloudflare has a straightforward REST API
    that we can use cURL to communicate with directly, without the extra
    start-up cost.
    
    Let's do that instead, and move this to run in the
    deploy-to-github-pages action, which is run from multiple entry points,
    all of which will want to purge the Cloudflare caches upon deployment.
    
    [1]: #1893 (comment)
    
    Signed-off-by: Taylor Blau <me@ttaylorr.com>
    ttaylorr committed Oct 4, 2024
    Configuration menu
    Copy the full SHA
    a641435 View commit details
    Browse the repository at this point in the history