Skip to content

Latest commit

 

History

History
32 lines (19 loc) · 1.68 KB

contributing.md

File metadata and controls

32 lines (19 loc) · 1.68 KB
Raw

Contributing

Contributions are welcome via Pull Requests on Github.

An interesting read is Contributing to a Github Project.

Also try to code in the same style as Laravel (which followes the PSR standard guidelines). StyleCI is set up to fix any discrepancies automatically!

If you want to run the test suite of Laravel Packager, try out the composer test or composer test-coverage commands.

Things To Do

If you want to contribute but do not know where to start, this list provides some starting points.

  • Test for several commands, as well as the different options.
  • Test the Conveyor and Wrapping on their own.
  • Test publish and tests command.
  • Removing a package leaves (multiple) whitespaces in app.php and composer.json. Can this be done differently?

Pull Requests

  • Add tests! - Your patch likely won't be accepted if it doesn't have tests.

  • Document any change in behaviour - Make sure the readme.md, changlog.md and any other relevant documentation are kept up-to-date.

  • Consider our release cycle - We try to follow SemVer v2.0.0. Randomly breaking public APIs is not an option.

  • One pull request per feature - If you want to do more than one thing, send multiple pull requests.

  • Send coherent history - Make sure each individual commit in your pull request is meaningful. If you had to make multiple intermediate commits while developing, please squash them before submitting.

Happy coding!