Ash Wilson

> I just want it to be possible to trigger builds via the webhook payload and let people figure out how to make the endpoint available to GitHub’s webhook posting....

> I simply want to have DCIY presume that people have keys/access set up themselves on the command line, so the app basically assumes that simply shelling out and calling...

How about: 1. Adding a `validate :repo, presence: true` in `Project` to catch the trivial case of "nothing there", and: 2. Capturing stderr and stdout from the [fetch and merge...

That's strange. @jwilm, are you still seeing this? I can't seem to reproduce it now:  Or even by building `master` off of your fork, which (properly) fails due to...

:+1: for the idea of doing an automatic push to a configured remote on build success. I would find this pretty much immediately useful, because it's how I deploy [azurefire](https://github.com/smashwilson/azurefire)....

I'm also fine with either MIT or ISC.

Hrm. Offhand I'd guess that this is a result of b1264de...

I'm trying to think of an alternative to this that might not be so CPU-hungry. The issue that commit addresses is that typing within a DisplayMarker doesn't fire a marker...

> By 'dirty' you mean the user modifying the content of a theirs or ours block? Yeah, that's it exactly -- "dirty" is what I call that in the code....

> ... I located this noting the @subscribe @statusBar, 'active-buffer-changed', @updateCursorPositionText and the subsequent updateCursorPositionText() would it be possible to limit this detecting dirty to an active tab by checking...