-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade phpcodesniffer-composer-installer #36791
Closed
Closed
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
7e80263
Upgrade phpcodesniffer-composer-installer
fredden 555a57d
Merge remote-tracking branch 'upstream/2.4-develop' into phpcs-installer
fredden 2770a59
Merge remote-tracking branch 'upstream/2.4-develop' into phpcs-installer
fredden 6afc2fa
Merge remote-tracking branch 'upstream/2.4-develop' into phpcs-installer
fredden aceddf6
Merge remote-tracking branch 'upstream/2.4-develop' into phpcs-installer
fredden 45a3ca4
Merge remote-tracking branch 'upstream/2.4-develop' into phpcs-installer
fredden 22ce531
Merge remote-tracking branch 'upstream/2.4-develop' into phpcs-installer
fredden 60c5edc
Merge remote-tracking branch 'upstream/2.4-develop' into phpcs-installer
fredden 0ddf6b7
Merge remote-tracking branch 'upstream/2.4-develop' into phpcs-installer
fredden 740a73c
Merge remote-tracking branch 'upstream/2.4-develop' into phpcs-installer
fredden 6537888
Merge remote-tracking branch 'upstream/2.4-develop' into phpcs-installer
fredden 397b196
Merge remote-tracking branch 'upstream/2.4-develop' into phpcs-installer
fredden 708d0f2
Merge remote-tracking branch 'upstream/2.4-develop' into phpcs-installer
fredden 2ef3c63
Merge remote-tracking branch 'upstream/2.4-develop' into phpcs-installer
fredden File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As same as for codding-standard repo PR I believe that
"^1.0"
will be enoughThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's nothing here that's not compatible with
^0.7.0
. I've specifically kept this because I expect other packages may take a while to upgrade / allow the new version. If there's something that requires^0.7
, it'll work today, but not after merging if we change this to^1.0
only. Listing both supported versions means that interoperability with other packages is maintained; Composer will pick the "best" version, which is typically the highest mutually-supported version. If we use^1.0
only here, then we're forcing others to upgrade their packages in order for their coding standard to be used in conjunction with this product.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Make sense