docs/managing-third-party/README.md
[TOC]
Before reading documentation in this directory, please check the general policies in Adding third_party Libraries. You MUST obtain the required approvals before adding a third-party dependency and accept the responsibility as a dependency owner.
This directory contains how-to guides on managing your dependency with autoroll tooling (aka. well-lit paths). Please refer to individual files to understand their use cases and constraints. You should adopt one well-lit path that suits your need (e.g. code organization, need for patching).
You can request to be exempted from the well-lit paths, please refer to Autoroll Exceptions.
If you are not sure which path to take, please file a bug in "Chromium > Third Party > Freshness" component for consultation.
If you're a Googler, you can alternatively email [email protected].
Recommended for dependencies that are imported as Git submodules, and can be used without modifying the dependency's source code. You can add BUILD.gn rules and tests alongside your dependency.
Recommended for checked-in code (e.g. a subset of files), or if you need to patch upstream source code.