Delete the redundant space for kubectl symbol (iTerm2) #1205
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
✅ Deploy Preview for spaceship-prompt ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Runrioter
added
the
improvement
denysdovhan
approved these changes
Sep 19, 2022
|
hey @Runrioter this seems like a fix not feature, i've changed the commit type |
github-actions bot
pushed a commit
that referenced
this pull request
Sep 19, 2022
## [4.3.1](v4.3.0...v4.3.1) (2022-09-19) ### Bug Fixes * Delete the redundant space for kubectl symbol (iTerm2) ([#1205](#1205)) ([8ddbc81](8ddbc81))
|
🎉 This PR is included in version 4.3.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
@denysdovhan Sorry, it is a fix. 👍 |
Runrioter
added
bug
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.
Description
It is a bug from iTerm2 (and iOS terminal app)
iTerm2 fix this bug.(Since iTerm2 3.5.0beta7). Refer to
Also see #432