Lines Matching refs:branch
90 branch. Branches for specific purposes, for example, a module branch for
99 branch mirroring the master branch of the external repository. It
101 main branch, which should be 'zephyr'.
114 update a Zephyr module repository with the latest development branch tip,
122 Changes to the main branch of a module repository, including synchronization
134 Force-pushing to a module's main branch is not allowed.
147 pull request against the module's main branch, which may be merged using
161 **Updating modules by merging the upstream branch:**
163 branch (e.g. main branch, latest release branch, etc.) submitting the result in
164 pull request against the module main branch, and merging the pull request using
170 the downstream main branch.
198 main branch
217 responsibility to merge approved pull requests in the main branch of a
275 The merging of pull requests in the main branch of a module
1135 of the tree we use the commit hash, a tag, or a branch name. For pull requests
1168 in a special branch named ``zephyr``.