Skip to content

Conversation

@cseickel
Copy link
Contributor

@cseickel cseickel commented Mar 8, 2022

image

@cseickel cseickel force-pushed the feat/add-symbols-to-git-status branch 3 times, most recently from a101a97 to 8898d28 Compare March 8, 2022 03:38
@cseickel cseickel force-pushed the feat/add-symbols-to-git-status branch from 8898d28 to 04ca421 Compare March 8, 2022 03:41
@cseickel cseickel merged commit 158f106 into v2.x Mar 9, 2022
@nyngwang
Copy link

nyngwang commented Mar 10, 2022

When will this get merged into main? I really need this cool feature :3

@cseickel
Copy link
Contributor Author

This is part of a new, unreleased v2.x branch, which is my new main for a while. My plan is to leave main alone until v2.x is ready for release, then merge v2x to main and go back to using main as the dev branch. I'm not sure when that will be, probably this weekend or the next one.

The main reason for this is I want to consolidate the breaking changes before I subject people to them and give contributors a stable target to work against. I'd hate to see #164 be dropped because of a difficult rebase.

@nyngwang
Copy link

OK, I will wait. Don't need to hash this :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants