Merged
Conversation
Contributor
|
Did you run |
209c55d to
9212c3d
Compare
Author
|
It seems to have resolved the problem, so I think I hadn't run it. I did now and force pushed. |
Contributor
|
Thanks @Semphriss ! |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
I would like to update the Seti icons for VScode to the latest version. I'm not sure if there's a procedure, but I saw this line instructing me to open an update request; I hope I'm doing it right.
I've noticed that this seems to partially revert 3f02651; I ensured that I was using the latest version of jesseweed/seti-ui on the master branch when running
npm run update. I'm not sure if it's because the edits weren't there, or if there's another reason.