Conversation
Signed-off-by: Tomoya.Fujita <Tomoya.Fujita@sony.com>
There was a problem hiding this comment.
You can see the example reference with https://github.com/fujitatomoya/ros2ai/issues/new/choose
| @@ -0,0 +1,11 @@ | |||
| blank_issues_enabled: false | |||
There was a problem hiding this comment.
Do we need blank issue template?
There was a problem hiding this comment.
To be organization issue template, i think we can keep blank issue enabled. So that user can use sometimes if the template does not really match against what they are reporting.
| You can check the ROS Middleware (RMW) implementation with the command: `ros2 doctor --report` | ||
| Find the line starting with `middleware name` in the report. | ||
| validations: | ||
| required: true |
There was a problem hiding this comment.
maybe we can change this into if applicable to be general issue template for ros2 org, because some ros2 repositories do not need to have this information such as ros2_documentation.
| id: regression | ||
| attributes: | ||
| label: Regression | ||
| description: Is the reported bug a regression? If so, what is the last version of ROS where it still worked fine? |
There was a problem hiding this comment.
We can probably make it more general field to fill in.
| id: regression | |
| attributes: | |
| label: Regression | |
| description: Is the reported bug a regression? If so, what is the last version of ROS where it still worked fine? | |
| id: description | |
| attributes: | |
| label: Description | |
| description: Explain what the problem is. Besides, is the reported bug a regression? If so, what is the last version of ROS where it still worked fine? |
| @@ -0,0 +1,11 @@ | |||
| blank_issues_enabled: false | |||
There was a problem hiding this comment.
To be organization issue template, i think we can keep blank issue enabled. So that user can use sometimes if the template does not really match against what they are reporting.
|
part of ros2/ros2#1572