Skip to content

ci: report the required fuzz check on every PR#23

Merged
kriptoburak merged 1 commit into
mainfrom
codex/python-required-fuzz-check
Jul 24, 2026
Merged

ci: report the required fuzz check on every PR#23
kriptoburak merged 1 commit into
mainfrom
codex/python-required-fuzz-check

Conversation

@kriptoburak

@kriptoburak kriptoburak commented Jul 24, 2026

Copy link
Copy Markdown
Member

Summary

  • run the required Fuzz Query Strings workflow for every pull request
  • retain path filtering for ordinary pushes to main
  • preserve the existing scheduled and manual fuzz runs

Root Cause

Branch protection requires Fuzz Query Strings. The workflow also used pull-request path filters. A test-only contribution therefore skipped the workflow and remained permanently blocked, even after every applicable test passed.

GitHub documents that path-filtered required workflows remain pending and block merging. Required workflows must report a result for every protected pull request.

Impact

Every pull request now receives the required fuzz result. Runtime code, package metadata, public APIs, permissions, and fuzz behavior do not change.

Validation

  • actionlint .github/workflows/fuzz.yml
  • git diff --check
  • security, simplification, and maintainability reviews found no additional issue

Reference: https://docs.github.com/en/pull-requests/how-tos/merge-and-close-pull-requests/troubleshooting-required-status-checks

Signed-off-by: kriptoburak kriptoburak@users.noreply.github.com

Note

Run fuzz CI check on all pull requests targeting main

Removes the pull_request.paths filter from fuzz.yml so the fuzz workflow triggers on every PR, not just those touching previously listed paths. This ensures the fuzz check is always reported as a required status check regardless of which files are changed.

Macroscope summarized ee88637.

Signed-off-by: kriptoburak <kriptoburak@users.noreply.github.com>

@furkanerday furkanerday left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed the complete diff, PR description, all conversation and review history, unresolved threads, repository policies, relevant contracts and tests, required checks, and commit sign-offs at ee88637. All required checks pass, no actionable thread remains, and I found no blocking issue.

@kriptoburak
kriptoburak merged commit 4aad56f into main Jul 24, 2026
15 checks passed
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.

2 participants