Paul Gschwendtner f29fe5ced0 fix(dev-infra): use API pagination for retrieving project branches (#42666) ... We rely on a Github API `/branches` request to determine the active release trains. Currently this logic is broken if more than 100 protected branches exist within a repository. This issue surfaced recently where the `items_per_page` setting was set to `30`, causing the merge tooling and release tooling to not detect the proper "latest" release train. This commit uses Github pagination for retrieving branches to determine the active release trains, and makes the logic more long-term proof. PR Close #42666		2021-06-29 10:33:54 -07:00
..
build	fix(dev-infra): build with stamping for release builds (#42354)	2021-05-26 17:51:56 +00:00
config	feat(dev-infra): add support for determining if builds should be stamped (#42319)	2021-05-25 22:11:03 +00:00
info	feat(dev-infra): add command for printing release train information (#42644)	2021-06-28 11:50:57 -07:00
notes	refactor(dev-infra): improve type-safety of git client utility (#42468)	2021-06-03 14:34:33 -07:00
publish	refactor(dev-infra): update octokit to latest version v18 (#42666)	2021-06-29 10:33:54 -07:00
set-dist-tag	feat(dev-infra): Set up new common release notes generation tooling (#41905)	2021-05-06 09:40:29 -04:00
stamping	refactor(dev-infra): improve type-safety of git client utility (#42468)	2021-06-03 14:34:33 -07:00
versioning	fix(dev-infra): use API pagination for retrieving project branches (#42666)	2021-06-29 10:33:54 -07:00
BUILD.bazel	feat(dev-infra): add command for printing release train information (#42644)	2021-06-28 11:50:57 -07:00
cli.ts	feat(dev-infra): add command for printing release train information (#42644)	2021-06-28 11:50:57 -07:00