iSharkFly-Docs/angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-docs-cn/docs/COMMITTER.md
Joey Perrott e8ea839df8 docs: update docs to reflect new PR targeting methods for release trains (#38401) 
As part of the migration to a common strategy/method for branching and releasing across
the main angular repositories, updates need to be made to the documentation. These changes
reflect the updates made and is based on the following document which describes the
merging label expectations: https://docs.google.com/document/d/197kVillDwx-RZtSVOBtPb4BBIAw0E9RT3q3v6DZkykU

PR Close #38401
2020-08-27 14:52:04 -07:00

1.0 KiB
Raw Blame History

Pushing changes into the Angular tree

Please see Using git with Angular repositories for details about how we maintain a linear commit history and the rules for committing.

As a contributor, see the instructions in CONTRIBUTING.md.

Change approvals

Change approvals in our monorepo are managed via PullApprove and are configured via the .pullapprove file.

Merging

Once a change has all of the required approvals, either the last approver or the PR author (if PR author has the project collaborator status) should mark the PR with the action: merge label and the correct target label. This signals to the caretaker that the PR should be merged. See merge instructions.

Who is the Caretaker?

See this explanation.