Open christian-thomas opened 7 years ago
I already thought about all this - I love that we think the same 😉
That said, we don't need a timer. We could:
then we have timing perfectly based on commit history.
I'm unsure we can do it 'auto' on when tasks are all green but that could easily just auto execute my last point if I can find a way to do that.
Haha yeah, was a bit of a brain dump on things that it could do. I guess the only thing with no timer, would be that we'd need to calculate mm:ss from the commit logs, not a massive issue though I guess!
On Sat, Apr 22, 2017 at 20:35, Connor S. Parks notifications@github.com wrote: I'm unsure we can do it 'auto' on when tasks are all green but that could easily just auto execute my last point if I can find a way to do that.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub [https://github.com/industrious-mouse/challenge/issues/1#issuecomment-296396350] , or mute the thread [https://github.com/notifications/unsubscribe-auth/AAtLTOBW-FnhRDR-6GMPFJbce7D8E4eCks5rylZngaJpZM4NEixE] .
OK to use this it's pretty simple.
git clone git@github.com:industrious-mouse/challenge.git .
;composer install
;yarn
.author.json
with their details (Name + Email);yarn run start
;yarn run reset
.If there is an issue and somehow gulp dies (which I highly doubt) - don't run yarn run start
as it will reset the time tracking, you'll need to run yarn run resume
.
Just thinking about the best ways to automate this and mean we hopefully don't have to have too much intervention! Possible shell script to: