This repository was archived by the owner on Jan 6, 2026. It is now read-only.
Merged
Conversation
Rework the Cron GitHub actions to stop running the build by GitHub and trigger a new deployment on Cloudflare instead. This removes the inconsistency between pull request previews and cron deployments, where pull request previews were built by Cloudflare while cron deployments were built on GitHub. Additional changes: - Remove the GHA trigger for the main branch. The Cloudflare integration already watches the main branch and creates new deployments after a new commit was pushed. - Add manual trigger to allow us to test the functionality of this workflow or to manually re-run it after failures. Signed-off-by: Miroslav Bajtoš <oss@bajtos.net>
bajtos
requested review from
NikolasHaimerl,
juliangruber and
pyropy
as code owners
Deploying spark-dashboard with
|
| Latest commit: |
cf38e22
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://67367589.spark-dashboard.pages.dev |
| Branch Preview URL: | https://run-cron-deployment-on-cloud.spark-dashboard.pages.dev |
Signed-off-by: Miroslav Bajtoš <oss@bajtos.net>
juliangruber
suggested changes
Apr 7, 2025
Signed-off-by: Miroslav Bajtoš <oss@bajtos.net>
bajtos
commented
Apr 7, 2025
juliangruber
reviewed
Apr 7, 2025
Signed-off-by: Miroslav Bajtoš <oss@bajtos.net>
Member
Author
|
I am open-minded about which direction to take. I think all three options work:
|
Member
Author
|
Here is the scheduled GHA run using the old workflow that succeeded earlier today: https://github.com/CheckerNetwork/spark-dashboard/actions/runs/14300538033 
|
Member
Author
|
Today's scheduled run succeeded too. https://github.com/CheckerNetwork/spark-dashboard/actions/runs/14324837590 
|
Signed-off-by: Miroslav Bajtoš <oss@bajtos.net>
Signed-off-by: Miroslav Bajtoš <oss@bajtos.net>
juliangruber
approved these changes
Apr 9, 2025
Member
Author
|
I triggered a new run manually: https://github.com/CheckerNetwork/spark-dashboard/actions/runs/14355731060 
|
This was referenced Apr 9, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rework the Cron GitHub actions to stop running the build by GitHub and trigger a new deployment on Cloudflare instead.
This removes the inconsistency between pull request previews and cron deployments, where pull request previews were built by Cloudflare while cron deployments were built on GitHub.
Additional changes:
Remove the GHA trigger for the main branch. The Cloudflare integration already watches the main branch and creates new deployments after a new commit was pushed.
Add manual trigger to allow us to test the functionality of this workflow or to manually re-run it after failures.
This PR supersedes #41