patrick/zephyr
1
0
Fork 0
Code Issues Pull requests Actions 7 Packages Projects Releases Wiki Activity

templates: change template file namaes for proper sorting

Browse source 
prefix with numbers to get sorting based on usage. Most common files
issue types should come first, with bugs being at the top.

Signed-off-by: Anas Nashif <anas.nashif@intel.com>
This commit is contained in:
Anas Nashif 2023-06-08 10:17:25 +00:00
parent 65c9058ed4
commit c1e40bb3d5
13 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

0
.github/ISSUE_TEMPLATE/bug_report.md → .github/ISSUE_TEMPLATE/001_bug_report.md vendored
View file

0
.github/ISSUE_TEMPLATE/enhancement.md → .github/ISSUE_TEMPLATE/002_enhancement.md vendored
View file

0
.github/ISSUE_TEMPLATE/rfc-proposal.md → .github/ISSUE_TEMPLATE/003_rfc-proposal.md vendored
View file

0
.github/ISSUE_TEMPLATE/feature_request.md → .github/ISSUE_TEMPLATE/004_feature_request.md vendored
View file

0
.github/ISSUE_TEMPLATE/hardware_support.md → .github/ISSUE_TEMPLATE/005_hardware_support.md vendored
View file

0
.github/ISSUE_TEMPLATE/nomination.md → .github/ISSUE_TEMPLATE/006_nomination.md vendored
View file

0
.github/ISSUE_TEMPLATE/ext-source.md → .github/ISSUE_TEMPLATE/007_ext-source.md vendored
View file

0
.github/ISSUE_TEMPLATE/bin-blobs.md → .github/ISSUE_TEMPLATE/008_bin-blobs.md vendored
View file

2
doc/contribute/bin_blobs.rst
View file

@ -237,7 +237,7 @@ Follow the steps below to begin the submission process:
detail, so that you are informed of the criteria used by the TSC in order to detail, so that you are informed of the criteria used by the TSC in order to
approve or reject a request approve or reject a request
#. Use the :github:`New Binary Blobs Issue #. Use the :github:`New Binary Blobs Issue
<new?assignees=&labels=RFC&template=bin-blobs.md&title=>` to open an issue <new?assignees=&labels=RFC&template=008_bin-blobs.md&title=>` to open an issue
#. Fill out all required sections, making sure you provide enough detail for the #. Fill out all required sections, making sure you provide enough detail for the
TSC to assess the merit of the request. Additionally you must also create a Pull TSC to assess the merit of the request. Additionally you must also create a Pull
Request that demonstrates the integration of the binary blobs and then Request that demonstrates the integration of the binary blobs and then

2
doc/contribute/external.rst
View file

@ -131,7 +131,7 @@ Follow the steps below to begin the submission process:
detail, so that you are informed of the criteria used by the TSC and board in detail, so that you are informed of the criteria used by the TSC and board in
order to approve or reject a request order to approve or reject a request
#. Use the :github:`New External Source Code Issue #. Use the :github:`New External Source Code Issue
<new?assignees=&labels=RFC&template=ext-source.md&title=>` to open an issue <new?assignees=&labels=RFC&template=007_ext-source.md&title=>` to open an issue
#. Fill out all required sections, making sure you provide enough detail for the #. Fill out all required sections, making sure you provide enough detail for the
TSC to assess the merit of the request. Optionally you can also create a Pull TSC to assess the merit of the request. Optionally you can also create a Pull
Request that demonstrates the integration of the external source code and Request that demonstrates the integration of the external source code and

2
doc/contribute/guidelines.rst
View file

@ -994,7 +994,7 @@ Requirements for Treewide Changes
pull requests that are treewide changes pull requests that are treewide changes
- The person proposing a treewide change must create an `RFC issue - The person proposing a treewide change must create an `RFC issue
<https://github.com/zephyrproject-rtos/zephyr/issues/new?assignees=&labels=RFC&template=rfc-proposal.md&title=>`_ <https://github.com/zephyrproject-rtos/zephyr/issues/new?assignees=&labels=RFC&template=003_rfc-proposal.md&title=>`_
describing the change, its rationale and impact, etc. before any pull describing the change, its rationale and impact, etc. before any pull
requests related to the change can be merged requests related to the change can be merged

2
doc/contribute/proposals_and_rfcs.rst
View file

@ -51,5 +51,5 @@ either disagreement or not enough voiced opinions in order to proceed. Make sure
to either label it appropriately or include it in the corresponding GitHub to either label it appropriately or include it in the corresponding GitHub
project in order for it to be examined during the next meeting. project in order for it to be examined during the next meeting.
.. _`RFC template`: https://github.com/zephyrproject-rtos/zephyr/blob/main/.github/ISSUE_TEMPLATE/rfc-proposal.md .. _`RFC template`: https://github.com/zephyrproject-rtos/zephyr/blob/main/.github/ISSUE_TEMPLATE/003_rfc-proposal.md
.. _`Zephyr meetings`: https://github.com/zephyrproject-rtos/zephyr/wiki/Zephyr-Committee-and-Working-Group-Meetings .. _`Zephyr meetings`: https://github.com/zephyrproject-rtos/zephyr/wiki/Zephyr-Committee-and-Working-Group-Meetings

2
doc/project/project_roles.rst
View file

@ -63,7 +63,7 @@ level to the Zephyr GitHub repository.
You may nominate yourself, or another GitHub user, for promotion to the Triage You may nominate yourself, or another GitHub user, for promotion to the Triage
permission level by creating a GitHub issue, using the :github:`nomination permission level by creating a GitHub issue, using the :github:`nomination
template <new?assignees=&labels=Role+Nomination&template=nomination.md&title=>`. template <new?assignees=&labels=Role+Nomination&template=006_nomination.md&title=>`.
Contributors granted the Triage permission level are permitted to add reviewers Contributors granted the Triage permission level are permitted to add reviewers
to a pull request and can be added as a reviewer by other GitHub users. to a pull request and can be added as a reviewer by other GitHub users.