🚀 : Selective cache purges in Cloudflare after deploying with github actions

[xuelink]

Is your feature request related to a problem? Please describe.
Managing cache purges in Cloudflare after deploying with GitHub Actions can be cumbersome, especially when only specific resources need to be purged. Currently, the process involves purging the entire cache, which can lead to unnecessary cache invalidation and potential performance issues.

Describe the solution you'd like
I would like the ability to perform selective cache purges in Cloudflare after deploying with GitHub Actions. This means being able to specify particular URLs or resources that need to be purged from the cache, rather than purging the entire cache.

Describe alternatives you've considered
One alternative is to continue purging the entire cache, but this is inefficient and can impact performance. Another alternative is to manually purge specific URLs through the Cloudflare dashboard, but this is time-consuming and prone to errors.

Additional context
Integrating selective cache purges into the GitHub Actions workflow would streamline the deployment process and improve overall efficiency. It would also reduce the risk of unintended cache invalidation and ensure that only necessary resources are purged from the cache.

Ref: https://github.com/langxapp/website/blob/main/.github/workflows/deploy.yml

Contributor: @DH-555

If you want speed up process of this issue, please send 🚀 as a reaction.

[xuelink]

https://github.com/marketplace/actions/cloudflare-purge-cache @DH-555

[xuelink]

https://gist.github.com/xuelink/66219e872153ac7db79d4c9387e7918d