Repository navigation
[CI] Point drupal-rector dev-main job at fork branch with ParentClassScopeResolver fix - #8849
Merged
Merged
Conversation
…ScopeResolver fix
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.
The drupal-rector dev-main job broke after
ParentClassScopeResolverwas removed in #8838: the sibling rules that inject it can no longer be autowired, so the whole suite errors at container build.Fix PR against the drupal-rector fork the job builds on: samsonasik/drupal-rector#1
This points the clone at that branch so the job turns green again. Revert to the upstream branch once the fix is merged there.
Note: 8 unrelated
ActionAnnotationToAttributeRectorfixture failures remain in that suite from a separate change; this only addresses the container errors.