[PHPStan] Avoid removing bleeding edge from phar include, let user handle own phpstan configuration#4840
Merged
TomasVotruba merged 2 commits intomainfrom Aug 23, 2023
Merged
Conversation
…ndle own phpstan configuration
Member
|
@TomasVotruba it seems cause to explicitely |
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
3 participants
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.
Follow up to #4769, as Rector no longer autoloads all PHPStan configs
This is now handled fully by user configuration - #4798 👍
Ref 70fb9af
Ref rectorphp/rector#2431