Required check stuck as “Expected” when PR only touches `scripts/**` (workflow skipped by paths-ignore)

[benceruleanlu]

When a PR only changes files under scripts/** (e.g. scripts/downloadFrontend.js in PR #1479), the required status check build-and-test-e2e-windows / integration-windows-test stays in “Expected — Waiting for status to be reported” and blocks merging.

Why this happens

• The required check is produced by the reusable workflow call job build-and-test-e2e-windows in .github/workflows/debug_all.yml.
• .github/workflows/debug_all.yml has on.pull_request.paths-ignore (and push.paths-ignore) including scripts/**.
• So for script-only changes, the entire workflow is skipped, meaning the required check is never created/reported.

Impact

• If branch protection requires build-and-test-e2e-windows / integration-windows-test, script-only PRs become unmergeable unless checks are manually bypassed.

Possible fixes

1. Adjust .github/workflows/debug_all.yml paths-ignore so scripts/downloadFrontend.js (or all scripts/**) triggers the workflow.
2. Update branch protection required checks to not require this job when the workflow is path-filtered.
3. Add a manual escape hatch: allow running debug_all.yml via workflow_dispatch and ensure branch protection accepts manually-triggered runs.

Example

• PR add distribution flag when building frontend #1479

┆Issue is synchronized with this Notion page by Unito

[dosubot]

Hi, @benceruleanlu. I'm Dosu, and I'm helping the desktop team manage their backlog and am marking this issue as stale.

Issue Summary:

• The required status check build-and-test-e2e-windows / integration-windows-test remains stuck as "Expected" for PRs modifying only scripts/** files.
• This happens because the workflow is skipped due to paths-ignore settings, causing branch protection rules to block merging.
• You suggested possible fixes like adjusting paths-ignore, changing branch protection requirements, or enabling manual workflow triggers.
• No further comments or updates have been made on this issue.

Next Steps:

• Please let me know if this issue is still relevant with the latest version of the desktop app by commenting here.
• If I don’t hear back within 7 days, I will automatically close this issue.

Thanks for your understanding and contribution!