Conversation
Contributor
Author
|
The main code has been updated so it updates the branch directly, rather than generating a PR which has to be applied. |
Contributor
Author
|
Obsolete |
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
1 participant
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 PR depends on apache/infrastructure-pelican#92 which creates a Docker image for GFM builds.
The action now includes a checkout of the source.
This to ensure that the generated site branch is available.
Instead of configuring the builder with Python modules and building the GFM code, it uses a pre-built Docker image. This is faster.
Rather than generate a PR for the changes to the output branch, they are committed automatically (as is done by the existing Pelican Buildbot jobs). Also the action creates the branch if it does not exist.