michaelh/zephyr
1
0
Fork 0
Code Releases Activity

doc: fix links

Browse source 
Fix link to the issue templates.

Signed-off-by: Alexandre Rey <alx.rey@icloud.com>
This commit is contained in:
Alexandre Rey 2025-06-14 10:20:29 +02:00 • committed by Benjamin Cabé
commit 0c22a981e6
3 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

2
doc/contribute/external.rst
View file

@ -173,7 +173,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=007_ext-source.md&title=>` to open an issue <new?assignees=&labels=RFC&template=007_ext-source.yml>` 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

@ -924,7 +924,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=003_rfc-proposal.md&title=>`_ <https://github.com/zephyrproject-rtos/zephyr/issues/new?assignees=&labels=RFC&template=003_rfc-proposal.yml>`_
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/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=006_nomination.md&title=>`. template <new?assignees=&labels=Role+Nomination&template=006_nomination.yml>`.
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.