Hacker News new | past | comments | ask | show | jobs | submit login

Hmm... thinking about this further, it shouldn't be too hard to have a wrapper for my build script that stores the most recent pass/fail state, then automatically commits when that state changes. The trick would be not polluting the continuous integration or end-of-episode branches. I'm sure it can be done, but my git-fu is weak and it would take some research. Might be a good stretch goal reward if funding goes well...

Maybe this: in "draft mode", you automatically commit on all changes in pass/fail state. Then, at some point, you "publish", at which point you squash all the commits from commit X to HEAD whose message matches "[ON RED]".

I imagine git rebase -i X | sed -i "magic happens here" would do the job.

Thanks for the reply! Good luck with reaching the funding goal - interested to hear how things go and if you do work out a way to get the build script working as well.

Okay, I did it. :-) I'm not sure how useful/readable the result is, but check it out and let me know what you think.


Awesome! Thanks for making this happen. Have downloaded the git repository and will take a look soon.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact