forked from laravel/framework
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
d7f7734
commit 1d95144
Showing
1 changed file
with
26 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,26 @@ | ||
| # Laravel Contribution Guide | ||
|
|
||
| This page contains guidelines for contributing to the Laravel framework. Please review these guidelines before submitting any pull requests to the framework. | ||
|
|
||
| ## Which Branch? | ||
|
|
||
| **ALL** bug fixes should be made to the 4.x branch which they belong. Bug fixes should never be sent to the `master` branch unless they fix features that exist only in the upcoming release. | ||
|
|
||
| ## Pull Requests | ||
|
|
||
| The pull request process differs for new features and bugs. Before sending a pull request for a new feature, you should first create an issue with `[Proposal]` in the title. The proposal should describe the new feature, as well as implementation ideas. The proposal will then be reviewed and either approved or denied. Once a proposal is approved, a pull request may be created implementing the new feature. Pull requests which do not follow this guideline will be closed immediately. | ||
|
|
||
| Pull requests for bugs may be sent without creating any proposal issue. If you believe that you know of a solution for a bug that has been filed on Github, please leave a comment detailing your proposed fix. | ||
|
|
||
| ### Feature Requests | ||
|
|
||
| If you have an idea for a new feature you would like to see added to Laravel, you may create an issue on Github with `[Request]` in the title. The feature request will then be reviewed by a core contributor. | ||
|
|
||
| ## Coding Guidelines | ||
|
|
||
| Laravel follows the [PSR-0](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-0.md) and [PSR-1](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-1-basic-coding-standard.md) coding standards. In addition to these standards, below is a list of other coding standards that should be followed: | ||
|
|
||
| - Namespace declarations should be on the same line as `<?php`. | ||
| - Class opening `{` should be on the same line as the class name. | ||
| - Function and control structure opening `{` should be on a separate line. | ||
| - Interface names are suffixed with `Interface` (`FooInterface`) |