-
Notifications
You must be signed in to change notification settings - Fork 192
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
Refactor of git status #262
Conversation
I suggest you parse |
I agree with this. The main blocker I have here is that my ruby knowledge is pretty newbie and the syntax/concepts were tripping me up a lot just getting this into merge. I did revert this with #269 with the TODO being, learn enough ruby to parse |
I may be able to help with that; my Ruby chops are decent. I’ll try to find some time this week to check it out. |
That'd be awesome!_! You need any guidance at all about what we think needs
to get done to fit this sonny in, don't hesitate!
…On Mon, Sep 10, 2018 at 6:45 PM Jeff Byrnes ***@***.***> wrote:
I may be able to help with that; my Ruby chops are decent. I’ll try to
find some time this week to check it out.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#262 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAJyKnDgWB_fZHg0V18po_7QnhEKiUBwks5uZtYkgaJpZM4WVyjR>
.
|
@jeffbyrnes Thanks for the offer! I'd be willing to review your code. |
Haven‘t yet had any bandwidth to tackle this, sorry! One day soon, I hope. |
Long time coming. Let's dogfood this for a bit, but I think it'll work well. I left the legacy version in the source code for now so it's a little bit easier to hack it back in if this break anything for anyone.