templates: change template file namaes for proper sorting 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>
diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/001_bug_report.md similarity index 100% rename from .github/ISSUE_TEMPLATE/bug_report.md rename to .github/ISSUE_TEMPLATE/001_bug_report.md
diff --git a/.github/ISSUE_TEMPLATE/enhancement.md b/.github/ISSUE_TEMPLATE/002_enhancement.md similarity index 100% rename from .github/ISSUE_TEMPLATE/enhancement.md rename to .github/ISSUE_TEMPLATE/002_enhancement.md
diff --git a/.github/ISSUE_TEMPLATE/rfc-proposal.md b/.github/ISSUE_TEMPLATE/003_rfc-proposal.md similarity index 100% rename from .github/ISSUE_TEMPLATE/rfc-proposal.md rename to .github/ISSUE_TEMPLATE/003_rfc-proposal.md
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/004_feature_request.md similarity index 100% rename from .github/ISSUE_TEMPLATE/feature_request.md rename to .github/ISSUE_TEMPLATE/004_feature_request.md
diff --git a/.github/ISSUE_TEMPLATE/hardware_support.md b/.github/ISSUE_TEMPLATE/005_hardware_support.md similarity index 100% rename from .github/ISSUE_TEMPLATE/hardware_support.md rename to .github/ISSUE_TEMPLATE/005_hardware_support.md
diff --git a/.github/ISSUE_TEMPLATE/nomination.md b/.github/ISSUE_TEMPLATE/006_nomination.md similarity index 100% rename from .github/ISSUE_TEMPLATE/nomination.md rename to .github/ISSUE_TEMPLATE/006_nomination.md
diff --git a/.github/ISSUE_TEMPLATE/ext-source.md b/.github/ISSUE_TEMPLATE/007_ext-source.md similarity index 100% rename from .github/ISSUE_TEMPLATE/ext-source.md rename to .github/ISSUE_TEMPLATE/007_ext-source.md
diff --git a/.github/ISSUE_TEMPLATE/bin-blobs.md b/.github/ISSUE_TEMPLATE/008_bin-blobs.md similarity index 100% rename from .github/ISSUE_TEMPLATE/bin-blobs.md rename to .github/ISSUE_TEMPLATE/008_bin-blobs.md
diff --git a/doc/contribute/bin_blobs.rst b/doc/contribute/bin_blobs.rst index 0f78194..f821cac 100644 --- a/doc/contribute/bin_blobs.rst +++ b/doc/contribute/bin_blobs.rst
@@ -237,7 +237,7 @@ detail, so that you are informed of the criteria used by the TSC in order to approve or reject a request #. 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 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
diff --git a/doc/contribute/external.rst b/doc/contribute/external.rst index 3d34710..8d0bf37 100644 --- a/doc/contribute/external.rst +++ b/doc/contribute/external.rst
@@ -131,7 +131,7 @@ detail, so that you are informed of the criteria used by the TSC and board in order to approve or reject a request #. 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 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
diff --git a/doc/contribute/guidelines.rst b/doc/contribute/guidelines.rst index 6238635..ee8d010 100644 --- a/doc/contribute/guidelines.rst +++ b/doc/contribute/guidelines.rst
@@ -994,7 +994,7 @@ pull requests that are treewide changes - 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 requests related to the change can be merged
diff --git a/doc/contribute/proposals_and_rfcs.rst b/doc/contribute/proposals_and_rfcs.rst index d181261..6333ecf 100644 --- a/doc/contribute/proposals_and_rfcs.rst +++ b/doc/contribute/proposals_and_rfcs.rst
@@ -51,5 +51,5 @@ to either label it appropriately or include it in the corresponding GitHub 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
diff --git a/doc/project/project_roles.rst b/doc/project/project_roles.rst index 4e2eeb8..95d38da 100644 --- a/doc/project/project_roles.rst +++ b/doc/project/project_roles.rst
@@ -63,7 +63,7 @@ You may nominate yourself, or another GitHub user, for promotion to the Triage 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 to a pull request and can be added as a reviewer by other GitHub users.