-
Notifications
You must be signed in to change notification settings - Fork 685
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.
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
Make issue templates consistent across repositories. #1572
Comments
Right now, there is only one template. Do we want to have multiple ones, as they did in the shared example? |
Nvm, the old template has two cases, one for bug report and one for feature request. |
@audrow can you take a look at, if they are good to go, i can open more PRs for other repositories with some cosmetic changes. |
There has been discussion on if we should have organization level issue templates instead of each repository.
IMO, organization issue templates would be the good option. (see my comments, ros2/rclcpp#2667) |
|
@gavanderhoorn i had no idea we have that issue already, i will open the for there, thanks 👍 |
A great example of what we could do for all repositories is ros2/launch#782 (review).
One known issue with our current issue template is that they point to ROS Answers, rather than the Robotics Stack Exchange.
The text was updated successfully, but these errors were encountered: