Skip to content

Commit 9fe4c95

Browse files
Ryanf55clalancette
andauthored
Add recommendation on example source PR (#4253)
* Add recommendation on example source PR * Other ROS devs could use an example directly in the docs for what is a source PR * Fix incorrect grammar Signed-off-by: Ryan Friedman <[email protected]> Signed-off-by: Ryan <[email protected]> Co-authored-by: Chris Lalancette <[email protected]>
1 parent 737b023 commit 9fe4c95

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

source/How-To-Guides/Releasing/Release-Team-Repository.rst

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -41,8 +41,7 @@ if a release team already exists for your project but you are not part of it.
4141
Start a new release team
4242
^^^^^^^^^^^^^^^^^^^^^^^^
4343

44-
Fill the `New Release Team issue <https://github.com/ros2-gbp/ros2-gbp-github-org/issues/new?assignees=&labels=&template=new_release_team.md&title=Add+release+team>`_ issue template
45-
if no release team exists for your project yet, request for a new release team to be created.
44+
If no release team exists for your project yet, fill out the `New Release Team issue <https://github.com/ros2-gbp/ros2-gbp-github-org/issues/new?assignees=&labels=&template=new_release_team.md&title=Add+release+team>`_ issue template to request one be created.
4645

4746
.. _what-is-a-release-repository:
4847

@@ -61,7 +60,7 @@ Having a release repository separate from your source code repository is a requi
6160
Create a new release repository
6261
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
6362

64-
If your repository is new to the ROS community, you should first open a pull request on `ros/rosdistro <https://github.com/ros/rosdistro>`_ adding a ``source`` entry for your repository.
63+
If your repository is new to the ROS community, you should first open a pull request on `ros/rosdistro <https://github.com/ros/rosdistro>`_ adding a ``source`` entry for your repository (e.g. https://github.com/ros/rosdistro/pull/39513).
6564
The review process for the rosdistro database will ensure your repository and packages conform to the `REP 144 package naming conventions <https://www.ros.org/reps/rep-0144.html>`_ and other requirements before release.
6665
Once your package name has been approved and merged, fill in the `Add New Release Repositories issue <https://github.com/ros2-gbp/ros2-gbp-github-org/issues/new?assignees=&labels=&template=new_release_repository.md&title=Add+new+release+repositories>`_ issue template
6766
if you don't have a release repo for your project yet.

0 commit comments

Comments
 (0)