ci: name fuzz.yml's path filter once for both triggers #481

Merged

natsukium merged 1 commit from ci/fuzz-paths-anchor into main 2026-09-26 11:58:16 +09:00

Conversation 0 Commits 1 Files changed 1 +2 -18

natsukium commented 2026-09-26 10:50:32 +09:00

Owner

Copy link

fuzz.yml's pull_request and push triggers carried the same 17-line paths list; the push trigger now aliases the pull_request one through a YAML anchor.

Open question this PR answers by its own CI: whether this Forgejo's workflow parser resolves anchors in on:. The file is in its own path filter, so a fuzz / cargo fuzz smoke run should appear on this PR. If it does not (or the workflow shows a parse error), close this PR.

`fuzz.yml`'s `pull_request` and `push` triggers carried the same 17-line `paths` list; the `push` trigger now aliases the `pull_request` one through a YAML anchor. Open question this PR answers by its own CI: whether this Forgejo's workflow parser resolves anchors in `on:`. The file is in its own path filter, so a `fuzz / cargo fuzz smoke` run should appear on this PR. If it does not (or the workflow shows a parse error), close this PR.

natsukium added 1 commit 2026-09-26 10:50:32 +09:00

ci: name fuzz.yml's path filter once for both triggers ... 73c5e9d64a

The pull_request and push triggers carried the same seventeen-line
exclusion list, and a crate added to one but not the other would make
the per-PR smoke and the main-branch smoke disagree about what can
break the fuzz targets. A YAML anchor keeps one list.

Assisted-by: Claude Code

natsukium scheduled this pull request to auto merge when all checks succeed 2026-09-26 10:54:50 +09:00

natsukium merged commit 6755dcaadd into main 2026-09-26 11:58:16 +09:00

natsukium deleted branch ci/fuzz-paths-anchor 2026-09-26 11:58:16 +09:00

natsukium referenced this pull request from a commit 2026-09-26 11:58:16 +09:00

ci: name fuzz.yml's path filter once for both triggers (#481)

Commenting is not possible because the repository is archived.

Reviewers

No reviewers

Labels

Clear labels   

priority/P0

Must be resolved before the v0.1.0 tag

  

priority/P1

Must be settled before the first public contract freezes

  

priority/P2

Explicitly deferred until after v0.1.0

  

release/v0.1.0

Work tracked for the first tagged release

  

status/blocked

Cannot start now: waits on an upstream release, another issue, or a recorded revisit trigger

  

status/planned

Triaged with a source-grounded plan and a passed pi review; ready to implement

  

type/bug

Shipped behavior that contradicts the docs or the code's own intent; needs a product code change

  

type/design

An open scope or trade-off question; needs a recorded decision in the owning explanation doc before code

  

type/test-gap

Documented or reviewed behavior that no test pins; usually split from a review finding, needs no product code change

  

type/tracker

Parent issue that tracks child work

No labels

priority/P0

priority/P1

priority/P2

release/v0.1.0

status/blocked

status/planned

type/bug

type/design

type/test-gap

type/tracker

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

natsukium/felis!481

No description provided.