Build: Update trigger conditions for Circle CI workflows

[valentinpalkovic]

Closes N/A

What I did

I have changed the CircleCI triggers so that CircleCI jobs aren't triggered when

• changing the PR from draft to reviewable and the other way around
• if labels are removed or added (except the labels ci:daily, ci:merged, ci:docs, ci:normal)

For testing purposes, I have changed the trigger event from pull_request_target to pull_request. As soon as the testing is done, I will revert this change!

Checklist for Contributors

Testing

The changes in this PR are covered in the following automated tests:

• stories
• unit tests
• integration tests
• end-to-end tests

Manual testing

Attention: The CircleCI tasks are triggered during testing because the pull_request_trigger event will always fire (inherited from the base branch). Because of that, please just look at the "Trigger CircleCI workflow" events.

Labels

1. Label the PR with ci:merged
2. Wait until the following actions have run successfully:

• Trigger CircleCI workflow / trigger-merged-tests (pull_request)
• Trigger CircleCI workflow / trigger-merged-tests (pull_request_trigger)

3. Add another label cli
4. Make sure that the Trigger CircleCI workflow / trigger-merged-tests (pull_request) was skipped
5. Push a change to the PR
6. Make sure that both mentioned actions at the top are executed
7. Remove the label cli
8. Make sure that the Trigger CircleCI workflow / trigger-merged-tests (pull_request) was skipped
9. Repeat steps 1-8, but use the following labels: ci:daily, ci:normal, ci:docs

Draft / Review

1. Label the PR with ci:merged
2. Wait until the following actions have run successfully:

• Trigger CircleCI workflow / trigger-merged-tests (pull_request)
• Trigger CircleCI workflow / trigger-merged-tests (pull_request_trigger)

3. Convert the PR to a draft
4. Make sure that the Trigger CircleCI workflow / trigger-merged-tests (pull_request) was skipped

Documentation

• Add or update documentation reflecting your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Checklist for 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:

  Available labels

  • bug: Internal changes that fixes incorrect behavior.
  • maintenance: User-facing maintenance tasks.
  • dependencies: Upgrading (sometimes downgrading) dependencies.
  • build: Internal-facing build tooling & test updates. Will not show up in release changelog.
  • cleanup: Minor cleanup style change. Will not show up in release changelog.
  • documentation: Documentation only changes. Will not show up in release changelog.
  • feature request: Introducing a new feature.
  • BREAKING CHANGE: Changes that break compatibility in some way with current major version.
  • other: Changes that don't fit in the above categories.

🦋 Canary release

This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the @storybookjs/core team here.

core team members can create a canary release here or locally with gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=<PR_NUMBER>

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit df6d614. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 1 target

• nx run-many -t build -c production --parallel=3

---

Sent with 💌 from NxCloud.