Paul Gschwendtner cb2ab26296 feat(dev-infra): merge script should link to original commit when cherry-picking with API strategy (#37889) ... The merge script uses `git cherry-pick` for both the API merge strategy and the autosquash strategy. It uses cherry-pick to push commits to different target branches (e.g. into the `10.0.x` branch). Those commits never point to the commits that landed in the primary Github branch though. For the autosquash strategy the pull request number is always included, so there is a way to go back to the source. On the other hand though, for commits cherry-picked in the API merge strategy, the pull request number might not always be included (due to Github's implementation of the rebase merge method). e.g. 27f52711c0 For those cases we'd want to link the cherry-picked commits to the original commits so that the corresponding PR is easier to track down. This is not needed for the autosquash strategy (as outlined before), but it would have been good for consistency. Unfortunately though this would rather complicate the strategy as the autosquash strategy cherry-picks directly from the PR head, so the SHAs that are used in the primary branch are not known. PR Close #37889		2020-07-07 12:16:21 -07:00
..
discover-new-conflicts	fix(dev-infra): support running scripts from within a detached head (#37737)	2020-06-26 09:51:09 -07:00
merge	feat(dev-infra): merge script should link to original commit when cherry-picking with API strategy (#37889)	2020-07-07 12:16:21 -07:00
rebase	fix(dev-infra): support running scripts from within a detached head (#37737)	2020-06-26 09:51:09 -07:00
BUILD.bazel	feat(dev-infra): create rebase-pr tool in ng-dev (#37055)	2020-05-18 16:18:32 -07:00
cli.ts	build: update license headers to reference Google LLC (#37205)	2020-05-26 14:26:58 -04:00