-
Notifications
You must be signed in to change notification settings - Fork 244
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
update documentation issue template #5859
Conversation
✅ Deploy Preview for odo-docusaurus-preview canceled.
|
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
@@ -3,7 +3,8 @@ name: Documentation | |||
about: Report mistakes or request for documentation | |||
--- | |||
|
|||
/kind documentation | |||
/area documentation | |||
/kind bug | |||
|
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.
While you're at it, can you also do something about the /kind cleanup
? I can create a new area/cleanup
label.
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.
I'm still not sure if /kind cleanup
make sense. that is probably for a longer discussion.
If we decide to do something with cleanup we can do it in a separate PR
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.
I'm still not sure if
/kind cleanup
make sense. that is probably for a longer discussion. If we decide to do something with cleanup we can do it in a separate PR
Then maybe remove the /kind cleanup
from the template because the label we currently have is deprecated, and keeping it in the template does not make sense.
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.
I'm confused :-/
I don't see any /kind cleanup
in this template for documentation.
This PR is supposed to clean up a template for documentation issues, nothing else.
If you are talking about a PR template, that is for a separate discussion in another PR.
/approve /override ci/prow/unit-and-validate-test |
@valaparthvi: Overrode contexts on behalf of valaparthvi: ci/prow/unit-and-validate-test, windows-integration-test/Windows-test In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: valaparthvi The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/area documentation
documentation should be in /area documentation
kind
is meant to be more like kind of an issue (bug, epic, user-story, feature request etc...)area
is to what area the issue/pr is related toeach issue or PR can have only one kind, but multiple areas