[size_diff] Do not enforce creep for newly added components

See https://crrev.com/c/4641156 for the related plugin change and
decision. Enforcing creep for newly added components is more likely than
not going to be a nuisance, since the introduction of a new bucket,
unless explicitly left "empty", will almost certainly exceed the creep
limit. This prevents workarounds like initializing empty buckets in one
CL and needing a follow-up CL, or otherwise asking for a spurious
Size-Review+1.

Change-Id: Id38e14dff518207de6050c7395e66fcef54bc55f
Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/infra/+/878892
Reviewed-by: Aaron Wood <aaronwood@google.com>
Commit-Queue: Auto-Submit <auto-submit@fuchsia-infra.iam.gserviceaccount.com>
Fuchsia-Auto-Submit: Anthony Fandrianto <atyfto@google.com>
2 files changed
tree: 732b92199d62accbfdfb5a8be340b6ec881f0f77
  1. artifacts/
  2. buildbucket/
  3. checkout/
  4. cmd/
  5. execution/
  6. flagutil/
  7. functools/
  8. gerrit/
  9. gitiles/
  10. monorail/
  11. rpcutil/
  12. scripts/
  13. third_party/
  14. vendor/
  15. .gitignore
  16. AUTHORS
  17. go.mod
  18. go.sum
  19. LICENSE
  20. manifest
  21. PATENTS
  22. README.md
README.md

infra

This repo contains tools and config files necessary to run infrastructure related to builds, code review, version control, and continuous integrations.