GitXplorerGitXplorer
g

eng-practices

public
20071 stars
1965 forks
16 issues

Commits

List of commits on branch master.
Verified
3bb3ec25b3b0199f4940b1aa75f0ac5c5753301c

Delete CNAME

aadambender committed 4 months ago
Verified
535bcf07cb15d5b828b59e3565dd2e30041634df

Create CNAME

aadambender committed 4 months ago
Verified
78c353112cde1ea7dfedf20c7e14ce8b11b801f8

Delete CNAME

aadambender committed 4 months ago
Verified
9af8c6fae5bfa95aef2f672546f5b544690879e0

Create CNAME

aadambender committed 4 months ago
Verified
21c4680ebda7779eeff87cd9c78f53deb6e784e7

Delete CNAME

aadambender committed 4 months ago
Verified
5d0d8d4211a7c92ed59eb42facdbe46b8c499a50

Create CNAME

aadambender committed 4 months ago

README

The README file for this repository.

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:

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", "patch", or "pull-request".
  • 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.

Creative Commons License