-
Notifications
You must be signed in to change notification settings - Fork 430
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
add issue templates. #2667
add issue templates. #2667
Conversation
Signed-off-by: Tomoya.Fujita <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need blank issue template?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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