Skip to content

fix: unblock required CI checks stuck on path-filtered workflows#1000

Open
Okorie2000-code wants to merge 1 commit into
Pulsefy:mainfrom
Okorie2000-code:fix/ci-path-filters-and-trigger-files
Open

fix: unblock required CI checks stuck on path-filtered workflows#1000
Okorie2000-code wants to merge 1 commit into
Pulsefy:mainfrom
Okorie2000-code:fix/ci-path-filters-and-trigger-files

Conversation

@Okorie2000-code

@Okorie2000-code Okorie2000-code commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

Summary

Fixes the root cause of PRs being permanently blocked with "Expected — Waiting for status to be reported" for all three required checks.

All three CI workflows (backend-checks, data-processing-checks, onchain-checks) only fire when files inside their respective apps/<area>/** directories change. Branch protection marks all three as required, so any PR touching other parts of the repo is stuck indefinitely and cannot be merged.

Linked Issue

Closes #1001

Type of Change

  • fix
  • chore

Changes

.github/workflows/

  • Added workflow_dispatch: to all three workflows — maintainers can now manually trigger checks from the Actions UI
  • Added each .ci-trigger sentinel file to its workflow's pull_request.paths filter

Sentinel files

  • Bumped apps/backend/.ci-trigger, apps/data-processing/.ci-trigger, apps/onchain/.ci-trigger — this PR itself triggers and validates all three checks

How contributors unblock future PRs

Add a one-line touch to the relevant .ci-trigger file in your PR if your changes don't naturally land in that app directory.

Validation

  • All three CI checks fire on this PR
  • Lint passed for affected area(s)

Checklist

  • Branch name uses fix/
  • Commit message follows Conventional Commits
  • PR scope matches linked issue acceptance criteria

@drips-wave

drips-wave Bot commented Jun 30, 2026

Copy link
Copy Markdown

Hey @Okorie2000-code! 👋 It looks like this PR isn't linked to any issue.

If this PR is for one of the issues assigned to you as part of a Wave, please link it to ensure your contribution is tracked properly. You can do this by adding a keyword to the PR description (e.g., Closes #123), or by clicking a button below:

Issue Title
#842 Backend: Idempotency keys for contract write endpoints Link to this issue

ℹ️ Learn more about linking PRs to issues

All three required CI checks (backend-checks, data-processing-checks,
onchain-checks) use `paths` filters on pull_request, so they only
fire when their respective apps/<area>/** files are changed. Branch
protection requires all three to pass, leaving any PR that doesn't
touch those directories permanently blocked with:

  Expected — Waiting for status to be reported

Changes:
- Add workflow_dispatch trigger to all three workflow files so
  maintainers can manually re-run checks from the Actions UI
- Add each .ci-trigger sentinel file to its workflow's pull_request
  paths filter so contributors can force a check by touching the file
- Bump all three .ci-trigger files to trigger all checks on this PR

Closes Pulsefy#1001
@Okorie2000-code Okorie2000-code force-pushed the fix/ci-path-filters-and-trigger-files branch from e6236cc to aeba890 Compare June 30, 2026 00:41
@Okorie2000-code Okorie2000-code changed the title fix: unblock required CI checks blocked by path filters fix: unblock required CI checks stuck on path-filtered workflows Jun 30, 2026
@Cedarich

Copy link
Copy Markdown
Contributor

Kindly update branch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix: CI required checks permanently blocked on PRs that don't touch app paths

2 participants