Add publish workflow, triggerable via API request #20726
Merged
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
Adds a new CircleCI workflow, which I will use to publish prereleases (`next` and `experimental`) for a given commit. The CircleCI API doesn't yet support triggering a specific workflow, but it does support triggering a pipeline. So as a workaround you can triggger the entire pipeline and use parameters to disable everything except the workflow you want. CircleCI recommends this workaround here: https://support.circleci.com/hc/en-us/articles/360050351292-How-to-trigger-a-workflow-via-CircleCI-API-v2- Eventually we can set this workflow to trigger on a cron schedule (once per week, for example).
facebook-github-bot
added
CLA Signed
React Core Team
acdlite
force-pushed
the
add-publish-workflow
branch
3 times, most recently
from
6766ffd
to
ae1c4b8
Compare
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit ae1c4b8:
|
Size changesComparing: 0935a1d...ae1c4b8 Stable channelNo significant bundle size changes to report. Experimental channelNo significant bundle size changes to report. |
bvaughn
approved these changes
Feb 3, 2021
koto
pushed a commit
to koto/react
that referenced
this pull request
Jun 15, 2021
Adds a new CircleCI workflow, which I will use to publish prereleases (`next` and `experimental`) for a given commit. The CircleCI API doesn't yet support triggering a specific workflow, but it does support triggering a pipeline. So as a workaround you can triggger the entire pipeline and use parameters to disable everything except the workflow you want. CircleCI recommends this workaround here: https://support.circleci.com/hc/en-us/articles/360050351292-How-to-trigger-a-workflow-via-CircleCI-API-v2- Eventually we can set this workflow to trigger on a cron schedule (once per week, for example).
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.
This doesn't actually implement the publish step. Just sets up a triggerable workflow that will eventually be used to publish.
Adds a new CircleCI workflow, which I will use to publish prereleases (
nextandexperimental) for a given commit.The CircleCI API doesn't yet support triggering a specific workflow, but it does support triggering a pipeline. So as a workaround you can trigger the entire pipeline and use parameters to disable everything except the workflow you want. CircleCI recommends this workaround here: https://support.circleci.com/hc/en-us/articles/360050351292-How-to-trigger-a-workflow-via-CircleCI-API-v2-
Eventually we can set this workflow to trigger on a cron schedule (once per week, for example).