HTML and CSS Reference
In-Depth Information
• Create a new topic branch to contain your feature, change, or fix ( git
checkout -b <topic-branch-name> ).
• Make sure that your changes adhere to the current coding conventions
used throughout the project; that is, indentation, accurate comments, and
so on.
• Commit your changes in logical chunks; use Git's interactive rebase
feature (more about this feature at help.github.com/articles/
interactive-rebase ) to tidy up your commits before making them
public. Please adhere to these Git commit message guidelines at tbag-
gery.com/2008/04/19/a-note-about-git-commit-mes-
sages.html or your pull request is unlikely be merged into the main pro-
ject.
• Locally merge (or rebase) the upstream branch into your topic branch.
• Push your topic branch up to your fork ( git push origin <topic-
branch-name> ).
• Open a pull request with a clear title and description. Please mention
which browsers you tested in.
This may seem like a lot of work, but it makes your pull requests significantly easier
to understand and faster to merge. Moreover, your code becomes the documenta-
tion of the work you have done and anyone who wants to know why that section
looks the way it does can go back to your commits and understand exactly why it is
the case.
Working on HTML5 Boilerplate would get you started with best practices of collabor-
ative development that you can take back to your workplace or any other collaborat-
ive work you do.
Search WWH ::




Custom Search