Ci/fix cloudflare pages deploy #78
Merged
Conversation
This file contains 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
NelsonBN
requested review from
matheusses,
marcelfernandes,
CristianoRC,
wilsonneto-dev and
giovannymassuia
wilsonneto-dev
approved these changes
Jan 26, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request includes changes to the GitHub Actions workflow for deploying to Cloudflare Pages. The main focus is to ensure that workflows are not triggered for pull requests from forked repositories.
Key changes:
.github/workflows/cloudflare-pages-deploy.yml: Added conditional checks to skip workflow steps if the pull request is from a forked repository. This includes skipping the build, cache restoration, dependency installation, build artifact upload, and deployment steps. [1] [2]Checklist before requesting a review