1.1 KiB
1.1 KiB
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 GitHub CODEOWNERS and are configured via the .github/CODEOWNERS 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 PR 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.