A pull request notifies repository maintainers that external changes are ready for review and possible merging into the main configuration. section 7.2.1
A feature-based workflow typically proceeds as follows:
- Create a branch for a ticket or change, modify the configuration, commit locally, and push the branch to a remote repository. section 7.2.1
- Open a pull request, add reviewers such as a change advisory board, and wait for approval. section 7.2.1
- Merge approved changes into the main branch; update other working branches from main before subsequent reviews. section 7.2.1
Firewall configuration changes
One contributor pushes TICKET-002, containing firewall-rule changes, and opens a pull request. After approval, the changes enter main. A teammate merges main into TICKET-005 before submitting a separate license update, reducing divergence between branches. section 7.2.1
Figure 7.11 When you use feature-based development, you isolate your changes to your branch and reconcile conflicts with the main configuration.
Shows how feature branches isolate changes and reconcile them with the main configuration. section 7.2.1
