Add separate workflow to build PRs from forks#264
Merged
MattiasBuelens merged 3 commits intomainfrom Apr 9, 2025
Merged
Conversation
Contributor
|
turbidwater
approved these changes
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
At the moment, we can't deploy pull request previews for forks due to a limitation of rossjrw/pr-preview-action (and also because of security considerations). However, we still want to run some checks on such PRs, so we can detect common problems like Markdown errors or broken links.
This adds a separate workflow specific for PRs from forks, which only builds the website without deploying it. The deploy preview workflow is now limited to run only on our own non-fork PRs.