• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..17-Apr-2020-

btree/H17-Apr-2020-1,7291,266

fields/H17-Apr-2020-1,322924

gapicgen/H17-Apr-2020-3,0912,395

kokoro/H17-Apr-2020-342176

leakcheck/H17-Apr-2020-193129

optional/H17-Apr-2020-174105

pretty/H17-Apr-2020-486359

protostruct/H17-Apr-2020-11676

testutil/H17-Apr-2020-734421

trace/H17-Apr-2020-164115

tracecontext/H17-Apr-2020-225172

uid/H17-Apr-2020-239156

version/H17-Apr-2020-12862

.repo-metadata-full.jsonH A D17-Apr-202029.1 KiB731730

README.mdH A D17-Apr-2020789 1813

annotate.goH A D17-Apr-20201.6 KiB5524

annotate_test.goH A D17-Apr-20201.8 KiB6643

retry.goH A D17-Apr-20201.7 KiB5529

retry_test.goH A D17-Apr-20202.4 KiB9064

README.md

1# Internal
2
3This directory contains internal code for cloud.google.com/go packages.
4
5## .repo-metadata-full.json
6
7`.repo-metadata-full.json` contains metadata about the packages in this repo. It
8is generated by `internal/gapicgen/generator`. It's processed by external tools
9to build lists of all of the packages.
10
11Don't make breaking changes to the format without consulting with the external
12tools.
13
14One day, we may want to create individual `.repo-metadata.json` files next to
15each package, which is the pattern followed by some other languages. External
16tools would then talk to pkg.go.dev or some other service to get the overall
17list of packages and use the `.repo-metadata.json` files to get the additional
18metadata required. For now, `.repo-metadata-full.json` includes everything.