Repository navigation
fix(ci): allow Psalm automatic parallelism in shared workflow - #116
Merged
Merged
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
--threads=1flag from the Psalm workflow distributed by the organization catalog.patches/nextcloud/psalm.yml.patchand the renderedworkflow-templates/psalm.ymltogether, preserving the pinned upstream source.--threads=autoneeded.Validation
composer run psalm -- --monochrome --no-progress --output-format=github).Rollout
After merging, consumer repositories such as
LibreSign/libresignmust synchronize their installedpsalm.ymlthrough the existing workflow updater and review the resulting PR. No consumer repository is changed by this PR alone.