Scribd
Upload
41 views2 pages

Can 5

The document discusses Laravel's guidelines for submitting bug reports and pull requests. It recommends including a title, clear description, relevant information, and code sample to replicate the bug. Bug reports aim to help others solve the problem collaboratively. Discussion of bugs and new features takes place on the Laravel Discord server and ideas can be proposed on the Laravel Ideas issue board. Fixes should be submitted to the latest stable branch, LTS branch, or master branch depending on the type of change.

Uploaded by

Bayu Indrawan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
41 views2 pages

Can 5

The document discusses Laravel's guidelines for submitting bug reports and pull requests. It recommends including a title, clear description, relevant information, and code sample to replicate the bug. Bug reports aim to help others solve the problem collaboratively. Discussion of bugs and new features takes place on the Laravel Discord server and ideas can be proposed on the Laravel Ideas issue board. Fixes should be submitted to the latest stable branch, LTS branch, or master branch depending on the type of change.

Uploaded by

Bayu Indrawan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Bug Reports

To encourage active collaboration, Laravel strongly encourages pull requests, not just bug reports.
"Bug reports" may also be sent in the form of a pull request containing a failing test.

However, if you file a bug report, your issue should contain a title and a clear description of the issue.
You should also include as much relevant information as possible and a code sample that
demonstrates the issue. The goal of a bug report is to make it easy for yourself - and others - to
replicate the bug and develop a fix.

Remember, bug reports are created in the hope that others with the same problem will be able to
collaborate with you on solving it. Do not expect that the bug report will automatically see any activity
or that others will jump to fix it. Creating a bug report serves to help yourself and others start on the
path of fixing the problem.

The Laravel source code is managed on GitHub, and there are repositories for each of the Laravel
projects:

 Laravel Application
 Laravel Art
 Laravel Documentation
 Laravel Cashier
 Laravel Cashier for Braintree
 Laravel Envoy
 Laravel Framework
 Laravel Homestead
 Laravel Homestead Build Scripts
 Laravel Horizon
 Laravel Passport
 Laravel Scout
 Laravel Socialite
 Laravel Telescope
 Laravel Website

Core Development Discussion


You may propose new features or improvements of existing Laravel behavior in the Laravel
Ideas issue board. If you propose a new feature, please be willing to implement at least some of the
code that would be needed to complete the feature.

Informal discussion regarding bugs, new features, and implementation of existing features takes place
in the #internals channel of the Laravel Discord server. Taylor Otwell, the maintainer of Laravel, is
typically present in the channel on weekdays from 8am-5pm (UTC-06:00 or America/Chicago), and
sporadically present in the channel at other times.
Which Branch?
All bug fixes should be sent to the latest stable branch or to the current LTS branch. Bug fixes
should never be sent to the master branch unless they fix features that exist only in the upcoming
release.

Minor features that are fully backwards compatible with the current release may be sent to the
latest stable branch.

Major new features should always be sent to the master branch, which contains the upcoming
release.

If you are unsure if your feature qualifies as a major or minor, please ask Taylor Otwell in
the #internals channel of the Laravel Discord server.

You might also like