Zaq? Question

@claytonrcarter @rsteube @prarit for visibility (if there's any opposition to moving over nows the time to voice it ;)

Welcome @mocha and @leipert -- they'll be aiding us on the GitLab side to get everything over. @leipert to post his thoughts on best approach. So far we've talked about...

> Might want to get #151 done first so that it won't interfere with any work profiles @rsteube Good point There are some small things we can do (called out...

@leipert Plan looks good, a couple notes: > Initial Setup CI: I've updated #409 so the tests are working now, I'm going to continue on to see if I can...

@leipert @mocha Reminder that lab currently uses the CC0 license: https://github.com/zaquestion/lab/blob/master/LICENSE Any friction there?

Need to fix the tests on GitLab, which all broke when the config changes happened I believe, but https://github.com/zaquestion/lab/pull/455 should be enough for us to make the cutover once that's...

@Atralb I need to reengage the folks at GitLab, to get this actually moving again, which I'm planning to do in the new year. That said, I'm planning to sort...

Released `0.18.0`, which doesn't change anything for this effort other than the first GitLab release being a higher version number.

@mrbrownt Can you share the git config for this and verify what version of lab you're running? It's very weird that we'd return the error like that. The lookup in...

The git docs don't make this any clearer: https://git-scm.com/docs/git-config#Documentation/git-config.txt-branchltnamegtremote But I did try this out locally and evidently you can set `branch..remote` directly to the remote url TIL Changes to...