Lines Matching +full:check +full:- +full:pr
15 The upstream MCUmgr repository is located `in this page <https://github.com/apache/mynewt-mcumgr>`_.
16 The Zephyr fork used in version 2.7 and earlier is `located here <https://github.com/zephyrproject-…
17 …rary that is `part of the Zephyr code base <https://github.com/zephyrproject-rtos/zephyr/tree/main…
27 … done directly to the Zephyr held code of the MCUmgr library, is backported to the ``v2.7-branch``.
28 … ported to the Zephyr held code from the upstream repository, is backported to the ``v2.7-branch``.
30 to the ``v2.7-branch``.
32 directly applied to the ``v2.7-branch``.
53 * The PR for the current version
54 * The SHAs of the commits, if the PR has already been merged
56 You must also apply the ``backport v2.7-branch`` label to the bug report.
61 You can either create a *backport pull request* or a *new-fix pull request*.
64 -------------------------------
84 #. Create the pull request selecting ``v2.7-branch`` as the merge target.
86 #. Update ``west.yml`` within Zephyr, creating a pull-request to update the MCUmgr library referenc…
89 Creating new-fix pull requests
90 ------------------------------
95 1. Create the pull request selecting ``v2.7-branch`` as the merge target.
97 #. Update ``west.yml`` within Zephyr, creating a pull-request to update the MCUmgr library referenc…
110 1. Check if the author has followed the correct steps that are required to apply the fix, as descri…
135 backport-<source>-<pr_num>-to_v2.7-branch
139 * ``upstream`` - if the fix has originally been merged to the upstream repository.
140 …* ``zephyr`` - if the fix has been applied to the Zephyr internal MCUmgr library (past 2.7 version…
144 For example, a branch named ``backport-upstream-137-to-v2.7-branch`` indicates a backport of pull
147 #. Push the reviewed pull-request branch to the newly created branch and merge the backport branch
148 to ``v2.7-branch``.
154 treatment. Apply the fix directly at the top of ``v2.7-branch``.
161 applied to the ``v2.7-branch`` of the MCUmgr.