Bizbee

@fkling That's really cool that you can supply your own custom handler! I haven't tried myself but I may give this a shot. I agree that the block comments are...

Sorry to post on such an old thread but this issue caused me some headache... The fact that the import fails silently can cause some tricky to find bugs. In...

@mhamann Sounds good, looking into it now. Just FYI this is my first PR so please let me know if I miss anything and i'll fix it 😄 . As...

Throwing out another potential option. If we are concerned with logging to stdout in production we could use the [debug](https://www.npmjs.com/package/debug) module. This would allow devs to opt-in to our logging...

Ah yes I see that now. Awesome, thanks again.

You can use the gitlab `except` directive and check for the marge user. ``` start_environment: stage: start_environment tags: - linux-docker dependencies: [] when: manual allow_failure: false except: variables: - $GITLAB_USER_LOGIN=~...

I spoke too soon unfortunately. The solution above resolves the issue when the marge service account rebases and pushes to the developers branch. It does *not* resolve the issue when:...