-
Notifications
You must be signed in to change notification settings - Fork 53
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
[FR]: Add new kurtosis feedback
flags
#219
Comments
@leeederek very aligned; when building the quickstart I used Wdyt if:
|
Hey @mieubrisse! Thanks for your feedback. I'm going to keep this Issue tightly scoped to the work required for adding new flags, and have created #226 to track the work required to swap the default operation in |
## Description: Was setting up the pre-reqs to build Kurtosis locally to test a #219 but noticed the formatting was off and hard to consume. This PR makes those instructions easier to read and follow. ## Is this change user facing? YES <!-- If yes, please add the "user facing" label to the PR --> <!-- If yes, don't forget to include docs changes where relevant --> ## References (if applicable): <!-- Add relevant Github Issues, Discord threads, or other helpful information. -->
## Description: Was setting up the pre-reqs to build Kurtosis locally to test a #219 but noticed the formatting was off and hard to consume. This PR makes those instructions easier to read and follow. ## Is this change user facing? YES <!-- If yes, please add the "user facing" label to the PR --> <!-- If yes, don't forget to include docs changes where relevant --> ## References (if applicable): <!-- Add relevant Github Issues, Discord threads, or other helpful information. -->
…nd docs` flags (#292) ## Description: Upgraded `kurtosis feedback` command docs, added the `bug, fr and docs` flags ## Is this change user facing? YES ## References (if applicable): tickets: #226 and #219 @leeederek you can review only this file: docs/docs/reference/cli/feedback.md because [there is another PR for the code](#287)
Background & current behavior
When I run:
kurtosis feedback "my feedback" --github
, I end up on the Github issues page where I then have to use the Github UI to select what kind of Issue to file (docs, feature request, or bug report).More often than not, I already know what kind of Github issue I want to file. Being able to specify my preferred feedback route using a flag to pass into the
kurtosis feedback
command would make it easier and smoother for me to submit feedback to the Kurtosis team.Desired behavior
I would like to see 3 new flags added to the
kurtosis feedback --github
command:kurtosis feedback "my feedback" --github --bug
a Github link opens up to the Bug Report Github issue template with the "Description and steps to reproduce" section pre-populated with "my feedback" (example)kurtosis feedback "my feedback" --github --fr
a Github link opens up to the Feature Request Github issue template with the "Background and current behavior" section pre-populated with "my feedback" (example).kurtosis feedback "my feedback" --github --docs
a Github link opens up to the Docs Issue Github issue template with the "Description of the issue" section pre-populated with "my feedback" (example).How important is this feature or improvement to you?
Painful, the lack of this feature makes using Kurtosis frictionful.
The text was updated successfully, but these errors were encountered: