Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: PHPCSStandards/composer-installer
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v0.6.0
Choose a base ref
...
head repository: PHPCSStandards/composer-installer
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v0.6.1
Choose a head ref
  • 5 commits
  • 2 files changed
  • 3 contributors

Commits on Jan 19, 2020

  1. Configuration menu
    Copy the full SHA
    0e4ba3f View commit details
    Browse the repository at this point in the history
  2. Merge pull request #102 from Dealerdirect/feature/readme-update-for-0…

    ….6-release
    
    Readme: minor tweak now 0.6.0 has been released
    Potherca authored Jan 19, 2020
    Configuration menu
    Copy the full SHA
    d8fa43d View commit details
    Browse the repository at this point in the history

Commits on Jan 26, 2020

  1. Fix for issue #103

    If the phpcodesniffer-composer-installer plugin is installed as a dev
    requirement and it is then uninstalled as part of a "--no-dev" install, a bug
    occurs. The bug that occurs is that the plugin complains that the  package
    "squizlabs/php_codesniffer" is not installed without checking if the package
    should be present.
    
    This commit adds a check to verify that this plugin is actually installed before
    complaining about the missing package. If this plugin itself is removed, then
    it should not complain about the missing package.
    Potherca committed Jan 26, 2020
    Configuration menu
    Copy the full SHA
    dc6d0e2 View commit details
    Browse the repository at this point in the history
  2. Change "is plugin uninstalled?" check to always run

    Previously the check would only run if the plugin was require-dev.
    That behaviour is incorrect, as the check should always be done.
    If the plugin is not installed, it doesn't make sense to return an
    error under any circumstances.
    
    This commit fixes that oversight.
    Potherca committed Jan 26, 2020
    Configuration menu
    Copy the full SHA
    8a008d5 View commit details
    Browse the repository at this point in the history

Commits on Jan 27, 2020

  1. Merge pull request #104 from potherca-contrib/issue/103-exit-code-on-…

    …unistall
    
    Fix for issue #103
    jrfnl authored Jan 27, 2020
    Configuration menu
    Copy the full SHA
    2a57571 View commit details
    Browse the repository at this point in the history
Loading