Searched +full:stale +full:- +full:pr +full:- +full:message (Results 1 – 6 of 6) sorted by relevance
| /Zephyr-latest/.github/workflows/ |
| D | stale_issue.yml | 1 name: "Close stale pull requests/issues"
4 - cron: "16 00 * * *"
7 stale:
8 name: Find Stale issues and PRs
9 runs-on: ubuntu-22.04
10 if: github.repository == 'zephyrproject-rtos/zephyr'
12 - uses: actions/stale@v9
14 stale-pr-message: 'This pull request has been marked as stale because it has been open (more
15 than) 60 days with no activity. Remove the stale label or add a comment saying that you
17 closed in 14 days. Note, that you can always re-open a closed pull request at any time.'
[all …]
|
| /Zephyr-latest/doc/project/ |
| D | modifying_contributions.rst | 19 * a developer cherry-picks commits submitted by other contributors into their
22 * integrate useful content which is part of a stale pull request, or
31 * drive stale pull requests to completion so they can be merged
37 A developer who intends to cherry-pick and potentially modify patches sent by
40 * clarify in their pull request the reason for cherry-picking the patches,
45 A developer who intends to force-push to a branch or pull request of
53 as *stale*. Read about how to identify pull requests as stale in
54 :ref:`development processes and tools <dev-environment-and-tools>`
60 the original sign-off line and author identity, or
62 *own* sign-off line and author identity). In this case, the developer
[all …]
|
| /Zephyr-latest/doc/contribute/ |
| D | contributor_expectations.rst | 1 .. _contributor-expectations:
10 - Reviewed more quickly and reviewed more thoroughly. It's easier for reviewers
12 to allocate large blocks of time to review a large PR.
14 - Less wasted work if reviewers or maintainers reject the direction of the
17 - Easier to rebase and merge. Smaller PRs are less likely to conflict with other
20 - Easier to revert if the PR breaks functionality.
32 - Smaller PRs should encompass one self-contained logical change.
34 - When adding a new large feature or API, the PR should address only one part of
38 - PRs should include tests or samples under the following conditions:
40 - Adding new features or functionality.
[all …]
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-3.3.rst | 14 * Introduced :ref:`USB-C <usbc_api>` device stack with PD (power delivery)
17 CMSIS-DSP as the default backend.
30 * CVE-2023-0359: Under embargo until 2023-04-20
32 * CVE-2023-0779: Under embargo until 2023-04-22
66 removed in favor of new :dtcompatible:`zephyr,flash-disk` devicetree binding.
71 * Starting from this release ``zephyr-`` prefixed tags won't be created
82 image states). Use of a truncated hash or non-sha256 hash will still work
88 registration function at boot-up. If applications register this then
93 application code, these will now automatically be registered at boot-up (this
129 This may cause out-of-tree scripts or commands to fail if they have relied
[all …]
|
| D | release-notes-2.0.rst | 12 * The kernel now supports both 32- and 64-bit architectures.
17 * We added support for :ref:`Point-to-Point Protocol (PPP) <ppp>`. PPP is a
20 * We added support for UpdateHub, an end-to-end solution for large scale
21 over-the-air device updates.
22 * We added support for ARM Cortex-R Architecture (Experimental).
32 * Fixes CVE-2019-9506: The Bluetooth BR/EDR specification up to and
35 negotiation. This allows practical brute-force attacks (aka "KNOB")
42 * New kernel API for per-thread disabling of Floating Point Services for
43 ARC, ARM Cortex-M, and x86 architectures.
45 * Additional support for compatibility with 64-bit architectures.
[all …]
|
| D | release-notes-3.2.rst | 13 * Added support for :ref:`bin-blobs` (also see :ref:`west-blobs`).
15 * Converted all supported boards from ``pinmux`` to :ref:`pinctrl-guide`.
31 * CVE-2022-2993: Under embargo until 2022-11-03
33 * CVE-2022-2741: Under embargo until 2022-10-14
56 This definition can be used by third-party code to compile code conditional
58 Therefore, any third-party code integrated using the Zephyr build system will
91 changed from ``-ENETDOWN`` to ``-ENETUNREACH``. A return value of ``-ENETDOWN`` now indicates
129 * Removed support for configuring the CAN-FD maximum DLC value via Kconfig
156 valid for specific bindings to specify like :dtcompatible:`gpio-leds` and
157 :dtcompatible:`fixed-partitions`.
[all …]
|
