fix(CI): some jobs are hanging

[fulopdaniel]

Fix CI checks showing "Expected — Waiting for status to be reported" on PRs that don't touch all packages

Problem

When workflows use paths filters, the entire workflow is skipped for PRs that don't touch matching files. A skipped workflow never reports any status at all -> GitHub never sees the job names it's waiting for, so required checks are stuck on "Waiting for status to be reported" indefinitely.

Solution

Each workflow now:

1. Always triggers on pull_request (no paths filter)
2. Runs a lightweight changes job using dorny/paths-filter@v3 to detect relevant file changes
3. skips/instantly passes the CI job if there are no relevant files touched.

Quirks

For matrix strategies (v3/v4 app bridge) the job instantly passes.
For single strategies the job is skipped.

This is due to some github quirks with matrix strategies.

Alternative approaches

We could run all the checks all the time.

[changeset-bot]

⚠️ No Changeset found

Latest commit: d4e60d3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[sonarqubecloud]

Quality Gate passed for 'App Bridge'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[ragi96]

@fulopdaniel but how is it done in the fondue packages? As they are not running everything and only the needed jobs are shown

[Copilot]

Pull request overview

This PR updates several GitHub Actions CI workflows to avoid required checks hanging on PRs that don’t touch certain packages, by removing pull_request.paths filters and adding an explicit “detect changes” gate job.

Changes:

• Remove pull_request.paths filters so workflows always start on PRs.
• Add a lightweight changes job using dorny/paths-filter@v3 to determine whether package-specific CI should run.
• Conditionally skip (or effectively no-op) downstream CI jobs when the relevant package files are unchanged.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 7 comments.

Show a summary per file

File	Description
.github/workflows/typing-continuous-integration.yml	Adds changes job and gates the sidebar-settings CI job based on detected path changes.
.github/workflows/guideline-themes-continuous-integration.yml	Adds changes job and gates theme lint/typecheck + tests based on detected path changes.
.github/workflows/guideline-blocks-continuous-integration.yml	Adds changes job and gates matrix-based guideline-blocks jobs based on detected path changes; extends matrix versions.
.github/workflows/cli-continuous-integration.yml	Adds changes job and gates the CLI CI job based on detected path changes.
.github/workflows/app-bridge-theme-continuous-integration.yml	Adds changes job and gates app-bridge-theme CI job based on detected path changes.
.github/workflows/app-bridge-continuous-integration.yml	Adds changes job and gates app-bridge CI + compatibility job based on detected path changes.
.github/workflows/app-bridge-app-continuous-integration.yml	Adds changes job and gates app-bridge-app CI job based on detected path changes.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[fulopdaniel]

@fulopdaniel but how is it done in the fondue packages? As they are not running everything and only the needed jobs are shown

@ragi96 Had a quick look but to me it seems like in fondue everything is always run. E.g. check this PR:
Frontify/fondue#2647 , the RTE component tests are run, even though it's not touched.

[ragi96]

@fulopdaniel but how is it done in the fondue packages? As they are not running everything and only the needed jobs are shown

@ragi96 Had a quick look but to me it seems like in fondue everything is always run. E.g. check this PR: Frontify/fondue#2647 , the RTE component tests are run, even though it's not touched.

But it's having paths: https://github.com/Frontify/fondue/blob/6c76ab618d7887b96e99b3fd9455746fc79a19f6/.github/workflows/charts-pull-requests.yaml#L6