HTML and CSS Reference
In-Depth Information
• A URL to the reduced test case (you can host one on jsfiddle.net or
codepen.io )
• Any other information that would be relevant to the bug, including lines of
code that might be the cause of the bug, and potential solutions
Ideally, a bug report should be self-contained, so contributors do not have to follow
up with you again to find out more about the bug and can instead focus on resolving
it.
Following this process to file a bug report is a learning experience in itself in how to
find out what is wrong with the markup, style, or script that you wrote.
Pull requests
If you have ideas on how to improve HTML5 Boilerplate, patches to fix some existing
issues, improvements or new features, you would submit what is known as a pull
request . A pull request is a set of changes you can submit for review to the HTML5
Boilerplate GitHub repository, so it can be reviewed by the core contributors and
merged into HTML5 Boilerplate if found to be useful.
A good way to start contributing would be to find a small issue that you think you can
fix, fork the GitHub project (learn more on what this means at help.github.com/
articles/fork-a-repo ), work on your changes and submit a pull request.
If your contribution changes a lot of lines of code and alters the nature of the project
drastically, consider opening an issue on the GitHub project first.
The following are the steps to get started with creating a pull request:
• Fork the project.
• Clone your fork (in your terminal, enter git
clone
ht-
tps://github.com/<your-username>/htm-
l5-boilerplate.git and press Enter ).
• Add an upstream remote (in your terminal enter git remote add up-
stream https://github.com/h5bp/html5-boilerplate.git
and press Enter ).
• Get the latest changes from upstream (for example, by entering git
pull upstream master and pressing Enter in your terminal).
Search WWH ::




Custom Search