aiden
/
depot_tools
mirror of https://chromium.googlesource.com/chromium/tools/depot_tools
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
main
chrome/4147
chrome/3987
chrome/3865
chrome/3904
infra/config
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'e7cc4c93c0'
${ noResults }
depot_tools/metadata
History
Jiewei Qian 1fbd216dbc metadata: expose validation result additional as a getter 
This permit downstream clients to retrieve the "source" text and do
their own formatting instead of relying on the format coded in
get_message().

Change-Id: Ia36cbd064ed0781bda76b09b064b97f6dc5e899e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5686730
Commit-Queue: Jiewei Qian <qjw@chromium.org>
Reviewed-by: Anne Redulla <aredulla@google.com>
 		10 months ago
..
fields Updating Revision presubmit to check for valid commit hash 10 months ago
tests metadata: expose validation result additional as a getter 10 months ago
OWNERS
…
PRESUBMIT.py [ssci] PEP8 formatting for metadata directory 2 years ago
README.md [ssci] Script to run validation on all metadata files 2 years ago
__init__.py Define main metadata validation functions 2 years ago
dependency_metadata.py metadata: define a clear DependencyMetadata interface 1 year ago
discover.py metadata: sort discovered files and validation messages 1 year ago
parse.py metadata: early terminate certain fields to avoid over extraction 1 year ago
scan.py metadata: sort result summary 1 year ago
validate.py metadata: sort discovered files and validation messages 1 year ago
validation_result.py metadata: expose validation result additional as a getter 10 months ago

README.md

Validation for Chromium's Third Party Metadata Files

This directory contains the code to validate Chromium third party metadata files, i.e. README.chromium files.

Prerequisites

  1. Have the Chromium source code checked out on disk
  2. Ensure you've run gclient runhooks on your source checkout

Run

metadata/scan.py can be used to search for and validate all Chromium third party metadata files within a repository. For example, if your chromium/src checkout is at ~/my/path/to/chromium/src, run the following command from the root directory of depot_tools:

vpython3 --vpython-spec=.vpython3 metadata/scan.py ~/my/path/to/chromium/src