- Chrome for Testing releases are built with `is_official_build` + `is_chrome_for_testing_branded`.
- Regular Chrome releases are built with `is_official_build` + `is_chrome_branded`.
- Chromium builds usually have none of these GN args set.
Any features conditional on `is_chrome_branded` are thus not supported in Chromium nor in CfT.
Bug: none
Change-Id: Ia8ecac55d93e2cca9abcb4fa3220293858cd7e17
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6021663
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
Auto-Submit: Mathias Bynens <mathias@chromium.org>
Previously we had a lot of documentation bundled in the `workflows.md`
file, which wasn't necessarily obvious to new users. The getting the
code documentation now lives in a dedicated file `get_the_code.md`,
which is also directly linked from the toplevel `README.md`, since
that's what developers are looking first.
It also rearranges the rest of the project documentation a bit to move
the most important things to the top, add [TOC]s everywhere and
streamlines the documentation around (3rd party) dependencies, as well
as updating the documentation on testing.
Bug: none
Change-Id: I7b5d9121c7f1137eeff7a4ff159816908ef10705
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4931037
Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
Auto-Submit: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Philip Pfaffe <pfaffe@chromium.org>
Mathias Bynens