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
..
check-target-branches	refactor(dev-infra): update octokit to latest version v18 (#42666)	2021-06-29 10:33:54 -07:00
checkout	build: upgrade angular build, integration/bazel and @angular/bazel package to rule_nodejs 2.2.0 (#39182)	2020-10-08 11:54:59 -07:00
common	refactor(dev-infra): improve type-safety of git client utility (#42468)	2021-06-03 14:34:33 -07:00
discover-new-conflicts	refactor(dev-infra): improve type-safety of git client utility (#42468)	2021-06-03 14:34:33 -07:00
merge	fix(dev-infra): use API pagination for retrieving project branches (#42666)	2021-06-29 10:33:54 -07:00
rebase	refactor(dev-infra): improve type-safety of git client utility (#42468)	2021-06-03 14:34:33 -07:00
BUILD.bazel	feat(dev-infra): provide tooling to check what branches a pr targets (#39504)	2020-11-03 14:55:24 -08:00
cli.ts	feat(dev-infra): support --no-branch-prompt to suppress the merge tool branch target confirmation (#40528)	2021-01-25 10:45:57 -08:00