2017-01-27 01:30:42 -05:00
# Pushing changes into the Angular tree
2015-08-10 14:45:50 -04:00
Please see [Using git with Angular repositories ](https://docs.google.com/document/d/1h8nijFSaa1jG_UE8v4WP7glh5qOUXnYtAtJh_gwOQHI/edit )
2019-10-20 13:53:10 -04:00
for details about how we maintain a linear commit history and the rules for committing.
2015-08-10 14:45:50 -04:00
2019-10-20 13:53:10 -04:00
As a contributor, see the instructions in [CONTRIBUTING.md ](../CONTRIBUTING.md ).
2015-08-10 14:45:50 -04:00
2017-01-27 21:10:00 -05:00
# Change approvals
2015-08-10 14:45:50 -04:00
2021-04-03 09:52:53 -04:00
Change approvals in our monorepo are managed via [PullApprove ](https://docs.pullapprove.com/ ) and are configured via the [`.pullapprove.yml` ](../.pullapprove.yml ) file.
2015-12-21 13:02:09 -05:00
2017-01-27 21:10:00 -05:00
# Merging
2015-08-10 14:45:50 -04:00
2019-10-20 13:53:10 -04:00
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)
2020-08-10 15:46:56 -04:00
should mark the PR with the `action: merge` label and the correct [target label ](https://github.com/angular/angular/blob/master/docs/TRIAGE_AND_LABELS.md#pr-target ).
2019-10-20 13:53:10 -04:00
This signals to the caretaker that the PR should be merged. See [merge instructions ](CARETAKER.md ).
2015-08-10 14:45:50 -04:00
2017-01-27 21:10:00 -05:00
# Who is the Caretaker?
2015-08-10 14:45:50 -04:00
2017-01-27 21:10:00 -05:00
See [this explanation ](https://twitter.com/IgorMinar/status/799365744806854656 ).