iSharkFly-Docs
/
angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-docs-cn/dev-infra/pr/BUILD.bazel

16 lines
399 B
Python
Raw Permalink Normal View History

build: update to rules_nodejs v4.0.0-beta.0 (#42760) Updates the Bazel NodeJS rules to v4.0.0-beta.0. This is necessary so that the Angular components repo can update, and it's generally good to stay as up-to-date as possible with the Bazel rules as it's easy to fall behind, and updating early allows us to discover issues affecting our tooling earlier (where they are easier to address due to e.g. potential breaking change policy). PR Close #42760
2021-07-06 09:45:55 -04:00
load("//dev-infra:defaults.bzl", "ts_library")
feat(dev-infra): create tool to determine conflicts created by a PR (#37051) Creates a tool in ng-dev to determine the PRs which become conflicted by merging a specified PR. Often the question is brought up of how many PRs require a rebase as a result of a change. This script allows to determine this impact. PR Close #37051
2020-05-05 18:37:31 -04:00
ts_library(
name = "pr",
feat(dev-infra): integrate merge script into ng-dev cli (#37138) Integrates the merge script into the `ng-dev` CLI. The goal is that caretakers can run the same command across repositories to merge a pull request. The command is as followed: `yarn ng-dev pr merge <number>`. PR Close #37138
2020-05-15 11:21:01 -04:00
srcs = ["cli.ts"],
feat(dev-infra): create tool to determine conflicts created by a PR (#37051) Creates a tool in ng-dev to determine the PRs which become conflicted by merging a specified PR. Often the question is brought up of how many PRs require a rebase as a result of a change. This script allows to determine this impact. PR Close #37051
2020-05-05 18:37:31 -04:00
visibility = ["//dev-infra:__subpackages__"],
deps = [
feat(dev-infra): provide tooling to check what branches a pr targets (#39504) Create a command in the `ng-dev` toolset that allows user's to check what branches a PR will merge into based on its targeting. PR Close #39504
2020-10-28 20:14:40 -04:00
"//dev-infra/pr/check-target-branches",
feat(dev-infra): tooling to check out pending PR (#38474) Creates a tool within ng-dev to checkout a pending PR from the upstream repository. This automates an action that many developers on the Angular team need to do periodically in the process of testing and reviewing incoming PRs. Example usage: ng-dev pr checkout <pr-number> PR Close #38474
2020-08-14 19:49:07 -04:00
"//dev-infra/pr/checkout",
feat(dev-infra): integrate merge script into ng-dev cli (#37138) Integrates the merge script into the `ng-dev` CLI. The goal is that caretakers can run the same command across repositories to merge a pull request. The command is as followed: `yarn ng-dev pr merge <number>`. PR Close #37138
2020-05-15 11:21:01 -04:00
"//dev-infra/pr/discover-new-conflicts",
"//dev-infra/pr/merge",
feat(dev-infra): create rebase-pr tool in ng-dev (#37055) Creates a tool in ng-dev which rebases a PR automatically and pushes the rebase commits back to the PR. This is meant to be a replacement to the local merge script currently in the repo and currently has feature parity. PR Close #37055
2020-05-11 18:21:18 -04:00
"//dev-infra/pr/rebase",
feat(dev-infra): create tool to determine conflicts created by a PR (#37051) Creates a tool in ng-dev to determine the PRs which become conflicted by merging a specified PR. Often the question is brought up of how many PRs require a rebase as a result of a change. This script allows to determine this impact. PR Close #37051
2020-05-05 18:37:31 -04:00
"@npm//@types/yargs",
],
)