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

Jump to bottom

Update triage docs for close with lack of info. #13177

Merged
merged 2 commits into from
Dec 15, 2021
Merged

Update triage docs for close with lack of info. #13177

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
47e8592
Update triage docs for close with lack of info.
klaases Dec 15, 2021
b67af5b
Add escape char for bullet formatting.
klaases Dec 15, 2021
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
17 changes: 7 additions & 10 deletions site/content/en/docs/contrib/triage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -153,9 +153,9 @@ A sample response to ask for more info:

> I don’t yet have a clear way to replicate this issue. Do you mind adding some additional details. Here is additional information that would be helpful:
>
> \* The exact `minikube start` command line used
> \* The exact `minikube start` command line used
>
> \* The full output of the `minikube start` command, preferably with `--alsologtostderr -v=4` for extra logging.
> \* The full output of the `minikube start` command, preferably with `--alsologtostderr -v=4` for extra logging.
>
> \* The full output of `minikube logs`
>
Expand Down Expand Up @@ -209,18 +209,15 @@ Then: Label with `triage/duplicate` and close the issue.

If an issue hasn't been active for more than four weeks, and the author has been pinged at least once, then the issue can be closed.

>Hey @author -- hopefully it's OK if I close this - there wasn't enough information to make it actionable, and some time has already passed. If you are able to provide additional details, you may reopen it at any point by adding /reopen to your comment.
>Hi @author – is this issue still occurring? Are additional details available? If so, please feel free to re-open the issue by commenting with `/reopen`. This issue will be closed as additional information was unavailable and some time has passed.
>
>Here is additional information that may be helpful to us:
>Additional information that may be helpful:
>
>\* Whether the issue occurs with the latest minikube release
> \* Whether the issue occurs with the latest minikube release
>
>\* The exact `minikube start` command line used
>
>\* The full output of the `minikube start` command, preferably with `--alsologtostderr -v=3` for extra logging.
>
>\* The full output of `minikube logs`
> \* The exact minikube start command line used
>
> \* Attach the full output of minikube logs, run `minikube logs --file=logs.txt` to create a log file
>
>Thank you for sharing your experience!

Expand Down