| Name | Date | Size | #Lines | LOC | ||
|---|---|---|---|---|---|---|
| .. | 03-May-2022 | - | ||||
| actions/ | H | 29-Sep-2021 | - | 157 | 123 | |
| apidiff/ | H | 29-Sep-2021 | - | 341 | 253 | |
| btree/ | H | 29-Sep-2021 | - | 1,729 | 1,266 | |
| carver/ | H | 29-Sep-2021 | - | 785 | 654 | |
| detect/ | H | 29-Sep-2021 | - | 149 | 97 | |
| examples/ | H | 29-Sep-2021 | - | 938 | 838 | |
| fields/ | H | 29-Sep-2021 | - | 1,322 | 924 | |
| gapicgen/ | H | 29-Sep-2021 | - | 5,290 | 4,386 | |
| generated/snippets/ | H | 29-Sep-2021 | - | 152,939 | 62,518 | |
| godocfx/ | H | 29-Sep-2021 | - | 5,436 | 4,883 | |
| kokoro/ | H | 29-Sep-2021 | - | 605 | 317 | |
| leakcheck/ | H | 29-Sep-2021 | - | 193 | 129 | |
| optional/ | H | 29-Sep-2021 | - | 174 | 105 | |
| pretty/ | H | 29-Sep-2021 | - | 489 | 359 | |
| protostruct/ | H | 29-Sep-2021 | - | 116 | 76 | |
| pubsub/ | H | 29-Sep-2021 | - | 156 | 62 | |
| testutil/ | H | 29-Sep-2021 | - | 938 | 554 | |
| trace/ | H | 29-Sep-2021 | - | 166 | 117 | |
| tracecontext/ | H | 29-Sep-2021 | - | 225 | 172 | |
| uid/ | H | 29-Sep-2021 | - | 239 | 156 | |
| version/ | H | 29-Sep-2021 | - | 128 | 62 | |
| .repo-metadata-full.json | H A D | 29-Sep-2021 | 65.4 KiB | 1,560 | 1,559 | |
| README.md | H A D | 29-Sep-2021 | 789 | 18 | 13 | |
| annotate.go | H A D | 29-Sep-2021 | 1.6 KiB | 55 | 24 | |
| annotate_test.go | H A D | 29-Sep-2021 | 1.8 KiB | 66 | 43 | |
| retry.go | H A D | 29-Sep-2021 | 2.5 KiB | 86 | 50 | |
| retry_test.go | H A D | 29-Sep-2021 | 2.6 KiB | 96 | 70 |
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.