Home
last modified time | relevance | path

Searched full:backport (Results 1 – 18 of 18) sorted by relevance

/Zephyr-latest/.github/workflows/
Dbackport.yml1 name: Backport
11 backport:
12 name: Backport
22 contains(github.event.label.name, 'backport')
26 - name: Backport
27 uses: zephyrproject-rtos/action-backport@v2.0.3-3
30 issue_labels: Backport
31 labels_template: '["Backport"]'
Dbackport_issue_check.yml1 name: Backport Issue Check
14 backport:
15 name: Backport Issue Check
17 group: backport-issue-check-${{ github.ref }}
30 - name: Run backport issue checker
/Zephyr-latest/doc/services/device_mgmt/
Dmcumgr_backporting.rst56 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*.
63 Creating backport pull requests
72 To create a backport pull request, do the following:
115 The specific merging process depends on where the fix comes from and whether it is a *backport* or …
135 backport-<source>-<pr_num>-to_v2.7-branch
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
153 Merging a new fix, that is not a backport of either any upstream or Zephyr fix, does not require an…
/Zephyr-latest/scripts/release/
Dlist_backports.py120 class Backport(object): class
132 """Create a Backport object with the provided repo,
158 return Backport(repo, base, pulls)
162 """Create a Backport object with the provided repo,
187 return Backport(repo, base, pulls)
192 # could also automatically fix titles like "Automated backport of PR #1234"
197 title = Backport.sanitize_title(i.title)
206 obj['title'] = Backport.sanitize_title(i.title)
306 bp = Backport.by_included_prs(repo, args.base, set(args.includes))
308 bp = Backport.by_date_range(repo, args.base,
/Zephyr-latest/doc/security/
Dreporting.rst152 mailing list describing known embargoed issues, and their backport
154 to determine if they need to backport these changes to any internal
172 - Backport plans within the Zephyr project.
189 for backport pull requests (and associated issues). Additionally, it is
191 release manager that the backport pull request and issue are addressing
/Zephyr-latest/doc/project/
Dcode_flow.rst21 shall be done using backport pull requests.
Ddev_env_and_tools.rst343 * - :guilabel:`Backport`
344 - The PR is a backport or should be backported.
/Zephyr-latest/doc/releases/
Drelease-notes-2.7.rst1034 * :github:`39260` - [backport v2.7-branch] backport of #38292 failed
1053 * :github:`39022` - [backport v2.7-branch] backport of #38834 failed
1057 * :github:`38999` - [backport v2.7-branch] backport of #38407 failed
1068 * :github:`38904` - [backport v2.7-branch] backport of #38860 failed
1202 * :github:`38237` - [backport v2.6-branch] backport of #37479 failed
1224 * :github:`38145` - [backport v2.6-branch] backport of #37787 failed
1225 * :github:`38144` - [backport v2.6-branch] backport of #37787 failed
1714 * :github:`35983` - [backport v1.14-branch] backport of #35935 failed
1782 * :github:`34392` - [backport v2.5-branch] backport of #34237 failed
1783 * :github:`34391` - [backport v1.14-branch] backport of #34237 failed
[all …]
Drelease-notes-2.2.rst954 * :github:`21695` - Documentation issues on v1.14-branch block backport
1018 * :github:`21306` - ARC: syscall register save/restore needs backport to 1.14
Drelease-notes-1.14.rst131 * :github:`16414` - Backport west build --pristine
237 * :github:`21306` - ARC: syscall register save/restore needs backport to 1.14
330 * :github:`16414` - Backport west build --pristine
Drelease-notes-2.5.rst1832 * :github:`25314` - Bluetooth: controller: legacy: Backport conformance test related changes
1901 * :github:`18529` - fs/fcb: consider backport of mynewt fixes
Drelease-notes-2.3.rst1384 * :github:`15680` - "backport v1.14 branch" label: update description and doc
Drelease-notes-2.0.rst1044 * :github:`16414` - Backport west build --pristine
Drelease-notes-2.4.rst1369 * :github:`26499` - usermode: random: backport random syscall
Drelease-notes-3.2.rst2419 * :github:`46164` - scripts: release: ci checks for issues associated with backport prs
/Zephyr-latest/doc/safety/images/
Dzephyr-safety-process.svg1 …Backport / Bugfix </div></div></div></foreignObject><text x="459" y="279" fill="rgb(0, 0, 0)" font…
/Zephyr-latest/doc/develop/getting_started/
Dinstallation_linux.rst201 You can build from source, or use a backport from your distribution's package
/Zephyr-latest/scripts/kconfig/
Dkconfiglib.py57 Python 3 was supported, so this was a backport).