Skip to content

fix(ci): allow Psalm automatic parallelism in shared workflow - #116

Merged
vitormattos merged 1 commit into
mainfrom
fix/psalm-auto-threads-template
Nov 17, 2026
Merged

vitormattos merged 1 commit into
mainfrom
fix/psalm-auto-threads-template

Conversation

@vitormattos

Copy link
Copy Markdown
Member

Summary

  • Remove the explicit --threads=1 flag from the Psalm workflow distributed by the organization catalog.
  • Update patches/nextcloud/psalm.yml.patch and the rendered workflow-templates/psalm.yml together, preserving the pinned upstream source.
  • Let Psalm 7.5.0 use its default CPU-based worker selection; no explicit --threads=auto needed.

Validation

  • Verified the downstream patch applies cleanly to the pinned Nextcloud workflow source.
  • Verified the patched rendering exactly matches the generated catalog template.
  • Parsed YAML and checked the expected Psalm command (composer run psalm -- --monochrome --no-progress --output-format=github).
  • Checked the commit diff: only the patch and generated workflow changed; upstream vendor source untouched.
  • Repository CI (including actionlint, render consistency and tests) must still run on this PR.

Rollout

After merging, consumer repositories such as LibreSign/libresign must synchronize their installed psalm.yml through the existing workflow updater and review the resulting PR. No consumer repository is changed by this PR alone.

Remove the forced single-thread flag from the centrally maintained Psalm
workflow. Keep the Nextcloud source pinned and record the customization
in the downstream patch so future template renders preserve it.

Signed-off-by: Vitor Mattos <1079143+vitormattos@users.noreply.github.com>
@vitormattos
vitormattos merged commit d73f9a3 into main Nov 17, 2026
5 checks passed
@vitormattos
vitormattos deleted the fix/psalm-auto-threads-template branch November 17, 2026 12:41
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.

1 participant