Core Development Discussion

You can propose new features or improvements to Laravel's existing behavior in the Laravel Ideas Issue Board. If you propose a new feature, we'd like to ask you to complete at least some of the code required for that feature.

Informal discussions about bugs, new features, and implementation of new features take place in the #internals channel on the Laravel Discord. Taylor Otwell, the maintainer of Laravel, is usually on the channel from 8am to 5pm (UTC-06:00 UTC-06:00 or America/Chicago) on weekdays, and occasionally at other times.

Branch selection

All bug fixes should be sent to the latest stable branch or the current LTS branch . Bug fixes Never should be sent to the master branch unless the fix is ​​for a feature that will only be released in an upcoming release.

Minor 's Fully backwards compatible new features will be sent to the latest stable branch.

Major New features should be sent to the master branch, which contains upcoming Laravel releases.

If you're not sure whether your feature qualifies as primary or secondary, ask Taylor Otwell in the #internals channel on the Laravel Discord.

Compile Assets

If you commit changes that will affect compiled files, such as those stored in laravel/laravel For most files in resources/sass or resources/js in the library, please do not submit compiled files. Because of their large size, reviewers were unable to physically review them. This can be exploited to inject malicious code into Laravel. To prevent this from happening, all static assets are generated and submitted by the Laravel maintainer.

Security Vulnerability

If you discover a security vulnerability in Laravel, please email Taylor Otwell: taylor@laravel.com. He handles all security breaches promptly.

Coding style

Laravel follows PSR-2 coding conventions and PSR-4 automatically Load specification.

PHPDoc

The following is the correct way to write the Laravel documentation comments. Note that the @param attribute is followed by two spaces, the parameter type, two spaces, and finally the variable name:

/**
 * 在容器中注册绑定。
 *
 * @param  string|array  $abstract
 * @param  \Closure|string|null  $concrete
 * @param  bool  $shared
 * @return void
 * @throws \Exception
 */public function bind($abstract, $concrete = null, $shared = false){    //}

StyleCI

Don’t worry that your code style is not beautiful enough! After merging the pull request, StyleCI will automatically correct all styles and merge them into the Laravel repository. This allows us to focus more on the content of the contribution rather than the coding style.