Raphael Stolt
Raphael Stolt
Since the number of options keeps growing it would be considerable to allow their configuration via a dedicated configuration file. Whether this happens via a programmtic approach, like [done](https://github.com/FriendsOfPHP/PHP-CS-Fixer/blob/master/src/ConfigInterface.php) by...
Refactor the API calls towards [Travis CI API v3](https://api.travis-ci.org/v3/). The v2 API will be deprecated by the end of 2017.
Similar to [package-sync](https://github.com/spatie/package-sync) there could/should be a command to check a package for [PDS](http://php-pds.com/) compliance which could/should also [fix](https://github.com/spatie/package-sync#fixing-package-issues) found issues.
It would be nice to distribute `construct` via a PHAR file.
When using the options `--github` or `--github-templates` a pre-populated [SUPPORT.md](https://github.com/blog/2400-support-file-support) file should be generated into the `.github` directory.
To also support users opting for `GitLab`, it would be useful to aid them in `constructing` a package structure targeted for GitLab. This could be done by introducing a `--profile`...
The `.construct` configuration should (also) be loaded from `$HOME/.config` and it should be recommended in the `README.md` to put it there instead of directly into `$HOME`.
Using the option to be e.g. `--parallel-lint` or simply `--lint` would add the [PHP Parallel Lint](https://github.com/JakubOnderka/PHP-Parallel-Lint) package as a development dependency, add related Composer scripts e.g. `lint` and `lint-changes`, and...
The generated Composer script _could_ be namespaced. With a new `--composer-script-namespace` option the namespace could be injected. When not set the Composer script namespace should be derived from the project...
Same as #122, though it might be possible that the constructed package will keep/have only a private scope (Satis, Toran Proxy).