Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reformat new release repository template. #296

Draft
wants to merge 1 commit into
base: latest
Choose a base branch
from
Draft

Reformat new release repository template. #296

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 21 additions & 14 deletions .github/ISSUE_TEMPLATE/new_release_repository.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,21 +4,28 @@ about: Add release repositories to an existing release team.
title: 'Add new release repositories'
---

<!--
Which release team will maintain these repositories?
If you do not yet have a release team in the ros2-gbp-github-org project, please instead use the [new release team](https://github.com/ros2-gbp/ros2-gbp-github-org/issues/new?assignees=&labels=&projects=&template=new_release_team.md&title=Add+release+team) template instead.
That template supports adding a new team and repositories at the same time.
-->
* Name of the release team:

* Release repositories to add:
<!--
Before release repositories are created, repositories and packages should be submitted to the official rosdistro repository https://github.com/ros/rosdistro for naming review.
The ros/rosdistro source entry link must be included for each repository.
Guidelines for package naming are describe in REP-144: https://www.ros.org/reps/rep-0144.html
<!--
Before release repositories are created, repositories and packages should be submitted to the official rosdistro repository https://github.com/ros/rosdistro for naming review.
Guidelines for package naming are describe in REP-144: https://www.ros.org/reps/rep-0144.html

If there are any existing release repositories which should have their contents imported into the ros2-gbp organization, list and link to them here.
Leave the checkbox _unchecked_. The ros2-gbp administrator will check the box when they have completed the repository import.
-->
* [FIRST_REPOSITORY](SOURCE URL)
* [ros/rosdistro source entry](LINK TO SOURCE FIELD IN ROS/ROSDISTRO)
* [ ] There is an existing release repository which should be imported: <RELEASE REPOSITORY URL>
* [SECOND REPOSITORY](SOURCE URL)
* [ros/rosdistro source entry](LINK TO SOURCE FIELD IN ROS/ROSDISTRO)
If you are requesting multiple repositories at once, please list them all here instead of creating multiple issues.
-->
* Release repositories to add:
* REPOSITORY NAME
<!--
The ROS project maintains an index of official ROS distributions and the packages that they contain.
Before a release repository is created, your repository must be listed in that index.
You can request that a new repostiory be added by submitting a pull request to https://github.com/ros/rosdistro
Once you have submitted the pull request, you may use it to complete and submit this issue.
However, the release repository will not be created until the ros/rosdistro pull request has been merged.
-->
If there are any existing release repositories which should have their contents imported into the ros2-gbp organization, list and link to them here.
Leave the checkbox _unchecked_. The ros2-gbp administrator will check the box when they have completed the repository import.
* [ ] There is an existing release repository which should be imported: <RELEASE REPOSITORY URL>
* ...