Joey Perrott 7a40d8cefd fix(dev-infra): use base ref name rather than sha for the githubTargetBranch (#41523) ... After updating to use the v4 graphql api in the merge tooling, the githubTargetBranch was set to be the sha of the latest commit rather than the branch name of the target branch. This caused our tooling to mismatch which branches were actually being targeted with the effect that if a PR targeted only the patch branch (i.e. labeled `target: patch` and targeting `11.2.x` in github)it would still expect to merge into both `11.2.x` and `master`. This is now corrected to once again use the branch name, restoring to the previous functionality. PR Close #41523		2021-04-08 15:18:02 -07:00
..
check-target-branches	fix(dev-infra): detect multiple target labels as invalid (#40156)	2021-01-11 09:56:22 -08: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	fix(dev-infra): run fetches in the git client in quiet mode (#39503)	2020-11-02 16:41:47 -08:00
discover-new-conflicts	refactor(dev-infra): create ng-dev executable locally in the repo (#39089)	2020-10-22 13:36:14 -07:00
merge	fix(dev-infra): use base ref name rather than sha for the githubTargetBranch (#41523)	2021-04-08 15:18:02 -07:00
rebase	refactor(dev-infra): set up new method for checking range of commits (#41341)	2021-04-01 11:30:26 -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