~~:warning: https://github.com/zeeshanu/git-profile/pull/11 needs to be merged first then I'll rebase this PR to remove extra commits from the previous PR~~

This PR adds more tests.

I converted exit() code to Exception to be able to test commands. Results are the same.

Coverage is far better :green_heart:

when execute git profile, here's what i got in terminal.

Git Profile version 1.0

usage:
  git profile [options] <command>

Commands:
  rm               Remove git profile
  add              Create a new git profile
  use              Change git profile locally or globally

Options:
  -h, --help       Display this help message
  -V, --version    Display this application version

didn't see the current or show method.

See https://git-scm.com/book/tr/v2/Git-Tools-Signing-Your-Work

Also:

• Move askQuestion & saveProfile to BaseCommand to avoid duplication
• Use simple-phpunit instead of phpunit (see http://symfony.com/doc/current/components/phpunit_bridge.html). Basically it display deprecated message from Symfony but also provide PHPUnit support for all version using the lowest available

Also I think phpcs is bit outdated and it should be better to use php-cs-fixer instead. I might be able to push an other PR with that change after that one got merged if you want.

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

:vertical_traffic_light: To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

Detected Package Files

• composer.json (composer)

Configuration Summary

Based on the default config's presets, Renovate will:

• Start dependency updates only once this Configure Renovate PR is merged
• Separate major versions of dependencies into individual branches/PRs
• Do not separate patch and minor upgrades into separate PRs for the same dependency
• Upgrade to unstable versions only if the existing version is unstable
• Raise PRs immediately (after branch is created)
• Use renovate/ as prefix for all branch names
• If semantic commits detected, use semantic commit type fix for dependencies and chore for all others
• Keep existing branches updated even when not scheduled
• Disable automerging feature - wait for humans to merge all PRs
• Ignore node_modules, bower_components, vendor and various test/tests directories
• Update existing lock files only when package.json is modified
• Autodetect whether to pin dependencies or maintain ranges
• Rate limit PR creation to a maximum of two per hour
• Limit to maximum 20 open PRs at any time
• Group known monorepo packages together
• Use curated list of recommended non-monorepo package groupings

:abcd: Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.

What to Expect

With your current configuration, Renovate will create 3 Pull Requests:

:children_crossing: Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or spam the project. See docs for prhourlylimit for details.

:question: Got questions? Check out Renovate's Docs, particularly the Getting Started section. If you need any further assistance then you can also request help here.

This PR has been generated by Renovate Bot. View repository job log here.

Looks like the fresh new 2.0 version wasn't update on packagist: https://packagist.org/packages/zeeshan/git-profile

Did you define the webhook on Github for auto update? Otherwise, could you update it on packagist?

Thanks!

Can you regenerate git-profile phar file and add new tag for new release?

Can you register your package on https://packagist.org for simple install via composer?

It would be really neato if you submitted this to Homebrew Cask Here's their guide on what to do https://github.com/caskroom/homebrew-cask/blob/master/doc/development/adding_a_cask.md

I would've suggested Homebrew Core but they don't like binaries in the core.

• Use php-cs-fixer to ensure coding standards
• Commit composer.lock to speed installation
• Fix command in README
• Update APPLICATION_VERSION to 2.0
• Use branch-alias to allow dev installation

This adds license information and keywords which Packagist will use in their search results. It also adds a latest release badge, a prettier build status and a license badge.

For open source projects we can use Travis CI to show the build status of a library. You will however need to configure the integration with this repository and create a Travis account.

https://travis-ci.org/getting_started