ci: job conditions without || next to needs #9

Merged
noe.trevino merged 1 commit from fix-job-conditions into main 2026-10-03 22:45:30 -05:00
Owner

In a called workflow, Forgejo rewrites needs.X and drops the parentheses in the job condition. The release job from #8 then ran on a pull request run in haunt.nvim. The docs job had the same fault.

The conditions now use only && and contains(fromJSON(...)). Tested on haunt.nvim#123: docs and release both skip on the PR run.

In a called workflow, Forgejo rewrites `needs.X` and drops the parentheses in the job condition. The release job from #8 then ran on a pull request run in haunt.nvim. The docs job had the same fault. The conditions now use only `&&` and `contains(fromJSON(...))`. Tested on haunt.nvim#123: `docs` and `release` both skip on the PR run.
In a called workflow, Forgejo rewrites needs.X and drops the parentheses in
the job condition. The release job's condition became
'... || needs.docs.result == 'skipped'', so it ran on a pull request run.
The docs job had the same fault and was only safe because tests succeeded.

The conditions now use only && and contains(fromJSON(...)).
noe.trevino deleted branch fix-job-conditions 2026-10-03 22:45:30 -05:00
Sign in to join this conversation.
No description provided.