ci: release workflow to open a PR on docs repo with latest changes #9583
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
crazy-max
commented
Jun 21, 2022
.github/workflows/dispatch-docs.yml
Outdated
| name: Sending ${{ env.EVENT_NAME }} event to ${{ env.UPSTREAM_OWNER }}/${{ env.UPSTREAM_REPO }} | ||
| uses: actions/github-script@v6 | ||
| with: | ||
| github-token: ${{ secrets.GHPAT_DOCS_DISPATCH }} |
There was a problem hiding this comment.
secret is in the org settings, no need to add it in this repo.
glours
approved these changes
Jun 21, 2022
|
Convert to draft for now, see docker/docs#14976 (comment) |
crazy-max
changed the title
|
As we can directly open a PR on docs repo from here there is no need to rely on dispatch events which avoid creating a workflow on docs repo: docker/docs#14976 (comment) PTAL @glours |
Signed-off-by: CrazyMax <[email protected]>
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.
closes #9296
follow-up docker/docs#14976
What I did
creates workflow with a release published types event. This workflow will be triggered when a release is published. The step in this workflow will send acompose-docsevent with a payload that contains the git context and release name from GitHub event as well as the dockerfile target that will be used upstream. here we use the officialactions/github-scriptaction instead of a community one to send the event.creates workflow with a release published types event. This workflow will be triggered when a release is published. The step in this workflow will clone the remote docs repository, build the
docs-referencestage in this repo and open a PR on docs repo with latest changes.cc @glours
Related issue
(not mandatory) A picture of a cute animal, if possible in relation with what you did
Signed-off-by: CrazyMax [email protected]