angular-docs-cn/.ng-dev
Paul Gschwendtner 4286b08b5d ci: exempt bazel scope from merge tool target label checks (#42869)
Currently, changes with the `bazel` scope are guarded by the
merge tool target label checks. i.e. feature commits with
the `bazel` scope cannot land in the patch branch. This is
expected for all public packages, but given the `bazel`
package being used internal-only, it should be possible
to land these in a patch branch. Especially since we want
tooling to be in sync between version branches as much
as possible.

PR Close #42869
2021-07-19 17:29:01 -07:00
..
caretaker.ts build: add configuration for caretaker handoff (#42859) 2021-07-15 13:34:59 -07:00
commit-message.ts build: remove commit message max line length limit (#41157) 2021-03-10 11:05:43 -08:00
config.ts feat(dev-infra): introduce new configuration for release tool (#38656) 2020-09-28 16:11:40 -04:00
format.ts build: wire up new CLDR generation tool within Bazel (#42230) 2021-07-16 12:44:59 -07:00
gitconfig build: adding shared .ng-dev/gitconfig file for convenience and consistent git config (#37951) 2020-07-13 09:23:03 -07:00
github.ts build: split dev-infra configuration into individual files (#37890) 2020-07-10 10:59:28 -07:00
merge.ts ci: exempt bazel scope from merge tool target label checks (#42869) 2021-07-19 17:29:01 -07:00
release.ts build: properly handle whether builds should be stamped for release (#42319) 2021-05-25 22:11:03 +00:00