[wiki] Fix branch-protection publishing flow (#48)#49
Merged
Conversation
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
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.
Summary
Adopts the branch-protection-friendly wiki publishing flow for issue #48. Pull request updates now generate a PR-scoped wiki branch and commit the wiki submodule pointer back to the PR branch, while merged PRs targeting
mainpublish the PR wiki branch into the wiki main branch.Changes
.github/workflows/wiki.ymlinto PR preview and merged-PR publish jobs..github/wikito the generated wiki preview commit already present in this checkout.resources/github-actions/wiki.ymlso consumer stubs call the reusable workflow on PR preview and merged-PR publish events instead of only pushing frommain.Testing
git diff --checkpassed.ruby -e 'require "yaml"; %w[.github/workflows/wiki.yml resources/github-actions/wiki.yml].each { |file| YAML.load_file(file) }; puts "YAML OK"'passed.composer dev-toolscould not complete because the current lock/vendor state is missingtwig/twig: Composer reports thattwig/twigis required bycomposer.jsonbut is not present incomposer.lock.Closes #48