View source for Using the Github UI to Make Pull Requests

== Before making a pull request == <!--T:28--> 
</translate>
<translate>
<!--T:29-->
A hastily proposed pull request can hurt its chances of acceptance. Low quality proposals, proposals for previously rejected features, may be quickly rejected, which can be demotivating for the unprepared contributor. Laying some groundwork ahead of the pull request can make the process smoother.

<!--T:34-->
Although there is no single way to prepare for submitting a pull request, it is generally a good idea to pursue feedback from other project developers beforehand to ascertain that the pull request may be desirable. Although it may seem like a useful feature or bug fix, there may be reasons it cannot work that you have not considered (or could not know about).

<!--T:35-->
As a rule of thumb, receiving encouraging feedback from long-standing project developers, and particularly members of the core team or existing contributors, is a good indication that the pull request is worth pursuing.  To get feedback, we suggest you join the [https://volunteers.joomla.org/ Volunteers Portal] and join RingCentral (still referred to as Glip, just ask a team lead in the Volunteers portal to add you) to ask other developers.  Once you are ready, we suggest, before doing any code, you submit an issue to the [https://issues.joomla.org Joomla! issue tracker] with "RFC" at the beginning.  That will create a request for comments which will help you to identify any additional work or issues you may have to overcome to get your idea accepted.
</translate>

<translate>