feat: create bug ticket #2003
Merged
feat: create bug ticket #2003
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## main #2003 +/- ##
=====================================
Coverage 9.13% 9.13%
=====================================
Files 122 122
Lines 7359 7359
=====================================
Hits 672 672
Misses 6642 6642
Partials 45 45 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
exu
reviewed
Aug 5, 2022
nicufk
approved these changes
Aug 5, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull request description
Closes #1937
This PR opens a browser with a new issue from the command line populating the versions and pointing to
debug infoto add more context.Adding the exact logs this way is not possible due to URL size limitations - the body of the issue is added as a URL param.
Shortening the logs to match the size limitations ends us up with a few characters from each pod - in scaled up Testkube clusters this might be even worse.
Another option would be to create the Issue using the GitHub API without opening a browser window. This would depend to have logging into GitHub implemented which we currently don't have - and it is not worth the effort at this point.
Checklist (choose whats happened)
Breaking changes
Changes
Fixes