laravel/laravel — pull request #1100 by franzliedke (2012-08-15 15:52:59+00:00)
Title: [Docs] Pull request guidelines

Since I messed up so badly with some of my last pull requests (introduced new bugs etc.) and seeing how the Illuminate codebase diverges from the Laravel3 one, thus still having some of the bugs that were fixed in the Laravel core repo. This could be avoided or at least made obvious by introducing regression tests when fixing bugs.

Very strict pull request guidelines would also reduce a little bit of workload on the core team, keep code quality high and teach contributors a lot. That is quite important - Gina Trapani's ThinkUp project is a very good example of this.

As a small start, here's a proposal for some very basic pull request guidelines, mentioning documentation and unit tests. (Travis CI integration would be a big plus here. Cough.)

I'm not the best writer, so maybe someone should go over this and extend it in some places.

I am also hoping for some input on the general guidelines, but I thought this needed a start... :)