Publish catalog generations through pull requests - #33
Merged
Merged
Conversation
The Pages workflow pushes a changed catalog to automation/plugin-catalog, opens or updates its pull request, enables squash auto-merge and dispatches Website CI on the branch. It deploys only after master is exactly the squash of that proposal onto the verified source, so master accepts changes only through checked pull requests.
Git requires a committer identity before a real merge, and CI runners provide none.
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.
The Pages workflow pushes a changed catalog to automation/plugin-catalog, opens or updates its pull request, enables squash auto-merge and dispatches Website CI on the branch. It deploys only after master is exactly the squash of that proposal onto the verified source, so master accepts changes only through checked pull requests.