Maximize GitHub pull request templates

GitHub and its pull requests are the way to go in much of the developer community. Pull requests enable contributors to discuss the current change and maintain a change history for future contributors.

Problem: The problem in the code, either caused by a bug, or a business case that isn’t handled by the code. Examples:

Note that these examples above do not state the business problem. The lack of a solution to the business problem could indeed be the code problem, but it is not the problem itself. You should always describe the problem of the previous code. In addition, please be empathetic to future readers, and spend the extra few seconds to ensure a crisp, clear problem statement that most folks who have a basic knowledge of the code in the repository can understand now and in the future.

Solution: Details of the code changes. Bulleting this section is extra useful for larger pull requests. Examples:

Additional sections may be added to this format. Typically, adding additional sections after the problem and solution encourage everyone to complete the template up to the solution section, and at least think about the remaining sections. Sections that could be added include:

Related posts:

Whether it be scrapping the web to index pages, get your right Facebook posts, Netflix recommendation systems or be your Machine Learning algorithms that use to train your model, only with the right…

Creatures with aberrant chromosomes from Springfield Oregon artist Elizabeth Blue.

There are two ways of talking. One way holds the sway. Manufactured in the mind the second throw away Myths like riffs are rapid. And fill the room with sound. A way to play with fiction facts we…