Skip to content

CI: Skip CircleCI when no workflow argument is set#23436

Merged
JReinhold merged 1 commit into
storybookjs:nextfrom
zmarkan:skip-default-ci-workflow
Jul 13, 2023
Merged

CI: Skip CircleCI when no workflow argument is set#23436
JReinhold merged 1 commit into
storybookjs:nextfrom
zmarkan:skip-default-ci-workflow

Conversation

@zmarkan
Copy link
Copy Markdown
Contributor

@zmarkan zmarkan commented Jul 13, 2023

Closes #

What I did

Create a new CircleCI pipeline param called skipped to skip default workflow run when no external parameters are set (merged, normal, or schedule)

How to test

Commit and push - no workflow should run by default in CircleCI.

Checklist

  • Make sure your changes are tested (stories and/or unit, integration, or end-to-end tests)
  • Make sure to add/update documentation regarding your changes
  • If you are deprecating/removing a feature, make sure to update
    MIGRATION.MD

Maintainers

  • When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli/src/sandbox-templates.ts
  • Make sure this PR contains one of the labels below.

["cleanup", "BREAKING CHANGE", "feature request", "bug", "documentation", "maintenance", "dependencies", "other"]

@JReinhold JReinhold added the patch:yes Bugfix & documentation PR that need to be picked to main branch label Jul 13, 2023
@JReinhold JReinhold changed the title Skip the default CircleCI workflow when no workflow argument is set CI: Skip CircleCI when no workflow argument is set Jul 13, 2023
@JReinhold JReinhold added the build Internal-facing build tooling & test updates label Jul 13, 2023
@JReinhold JReinhold merged commit 471bd4d into storybookjs:next Jul 13, 2023
This was referenced Jul 13, 2023
@JReinhold JReinhold added the patch:done Patch/release PRs already cherry-picked to main/release branch label Jul 18, 2023
@ndelangen ndelangen removed the patch:yes Bugfix & documentation PR that need to be picked to main branch label Oct 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build Internal-facing build tooling & test updates patch:done Patch/release PRs already cherry-picked to main/release branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants