https://google.github.io/eng-practices/

Google's Engineering Practices documentation
https://google.github.io/eng-practices/

Last synced: about 1 month ago
JSON representation

Google's Engineering Practices documentation

• Host: GitHub
• URL: https://google.github.io/eng-practices/
• Owner: google
• License: other
• Created: 2019-09-04T20:47:01.000Z (almost 5 years ago)
• Default Branch: master
• Last Pushed: 2024-05-10T21:52:25.000Z (about 1 month ago)
• Last Synced: 2024-05-11T19:31:44.369Z (about 1 month ago)
• Homepage: https://google.github.io/eng-practices/
• Size: 78.1 KB
• Stars: 19,782
• Watchers: 657
• Forks: 1,928
• Open Issues: 13
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Lists

• awesome-engineering-team-management - Google Engineering Practices - Explains how to perform code reviews and how to submit them. (Engineering / Engineering Practices)
• awesome-engineering-team-management - Google Engineering Practices - Explains how to perform code reviews and how to submit them. (Engineering / Engineering Practices)
• awesome-practices - Google Engineering Practices - Collective experience of various best practices that were developed over time in Google. (Development)
• awesome-management - Google Engineering Practices Documentation - Best take away: (Roles / Engineers)
• awesome-ui-resources - Engineering Practices Guide
• awesome-engineering - Engineering Practices Guide

README

        
# 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](review/index.md), which are actually two

    separate sets of documents:

    *   [The Code Reviewer's Guide](review/reviewer/index.md)

    *   [The Change Author's Guide](review/developer/index.md)

## 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](LICENSE), which encourages you to share these documents. See

 for more details.