Add git status

[BobbyKostadinov]

Add git status

[stringparser]

👍 this would be a very good idea, just with the first thing that comes to mind that would make possible to do an easy and very efficient watcher with just one git status on the background.

[stephenlacy]

PR's welcome

[stringparser]

Ok I'll give it a go this next week.

[stringparser]

WTH... I'll do it today

[stringparser]

@stevelacy @BobbyKostadinov I would have been very easy but I've become greedy haha.

From my fork lib/status.js

The thing is, are we going to just plug the git status output to a callback and/or stdout? Or should it be a stream?.

If there is something one can do here is create a pipeline on the way of gulp.src. There is no need for globs here, just plain files running through. What do you think? Should I leave my little green bag aside and just plug there the the output, or not? Is just that seems pretty weird to parse the git status (because what is the point then) and don't pass it as a stream.

[stephenlacy]

Create it in the way of: https://github.com/stevelacy/gulp-git/blob/master/lib/rm.js
And return the status to gutil.log.
We first had all functions as through2 streams, but broke it out due to not needing streams or gulp.src for the functions.

[stringparser]

Ok, I see. Log the buffer and pass the stream.

Thanks!

[stephenlacy]

Actually before you start on it, is there a need for the stream?

Calling git.status() in a task should just log the status as is, without needing to pipe to a stream.
That would make it easier to construct, similar to this: https://github.com/stevelacy/gulp-git/blob/master/lib/reset.js

[stringparser]

Haha, there is really no need for a stream. I'll experiment with the idea separately and let you now. Simpler is better. This is just me feeling guilty about having valuable information and not doing something with it. I'll log the stdout status.

Talk you soon.