mirror of https://github.com/eng-practices/eng-practices.git synced 2024-12-21 20:30:15 +08:00

Google's Engineering Practices documentation

Go to file

Max Kanat-Alexander 7d38053d01 Merge pull request #1 from google/test_267425726 Internal change		2019-09-05 13:53:07 -07:00
review	Internal change	2019-09-05 12:18:58 -07:00
_config.yml	Set theme jekyll-theme-slate	2019-09-05 12:01:09 -07:00
LICENSE	Re-add LICENSE file that was squashed by the export.	2019-09-05 13:48:50 -07:00
README.md	Internal change	2019-09-05 11:59:27 -07:00

README.md

Google Engineering Practices Documentation

Google has many generalized engineering practices that cover all languages and all projects. These documents represent our collective experience of various best practices that we have developed over time. It is possible that open source projects or other organizations would benefit from this knowledge, so we work to make it available publicly when possible.

Currently this contains the following documents:

Google's Code Review Guidelines, which are actually two separate sets of documents:
- The Code Reviewer's Guide
- The Change Author's Guide

Terminology

There is some Google-internal terminology used in some of these documents, which we clarify here for external readers:

CL: Stands for "changelist," which means one self-contained change that has been submitted to version control or which is undergoing code review. Other organizations often call this a "change" or a "patch."
LGTM: Means "Looks Good to Me." It is what a code reviewer says when approving a CL.

License

The documents 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.