|Number of watchers on Github||24951|
|Number of open issues||262|
|Average time to close an issue||29 days|
|Average time to merge a PR||8 days|
|Open pull requests||126+|
|Closed pull requests||54+|
|Last commit||3 months ago|
|Repo Created||over 5 years ago|
|Repo Last Updated||3 months ago|
|Organization / Author|
|Do you use styleguide? Leave a review!|
|View open issues (262)|
|View styleguide activity|
|View TODOs for styleguide (19)|
|View on github|
|Book a Mock Interview With Me (Silicon Valley Engineering Leader, 100s of interviews conducted)|
Software engineers: It's time to get promoted. Starting NOW! Subscribe to my mailing list and I will equip you with tools, tips and actionable advice to grow in your career.
My play store can't open it
Every major open-source project has its own style guide: a set of conventions (sometimes arbitrary) about how to write code for that project. It is much easier to understand a large codebase when all the code in it is in a consistent style.
Style covers a lot of ground, from use camelCase for variable names to never use global variables to never use exceptions. This project (google/styleguide) links to the style guidelines we use for Google code. If you are modifying a project that originated at Google, you may be pointed to this page to see the style guides that apply to that project.
If your project requires that you create a new XML document format, the XML Document Format Style Guide may be helpful. In addition to actual style rules, it also contains advice on designing your own vs. adapting an existing format, on XML instance document formatting, and on elements vs. attributes.
The style guides in this project are licensed under the CC-By 3.0 License, which encourages you to share these documents. See https://creativecommons.org/licenses/by/3.0/ for more details.