News for hackers. Stuff that matters.
Re:Safer branching by josho on Thursday October 06, 2016 @02:20PM (#12654756)
Nope.

My command line git workflow should not require working through a GUI.

Now, if this was added as some git hooks, enforcing the policy from both the command line and GUI then I'd be impressed (and excited).

Re:Safer branching by alblue on Thursday October 06, 2016 @03:54PM (#12655542)
That's pretty much what Gerrit does. Works with any git client, since it's just dealing with pushes, and can. E configured to merge automatically or with a manual nudge once the tests pass. And you can do this all through the command line; no GUI needed.
Re:Safer branching by kannonboy on Thursday October 06, 2016 @02:28PM (#12654828)
Comic author here. For the command-line I use a post-checkout hook to display the build status of a commit whenever I switch commits:

https://bitbucket.org/tpettersen/bitbucket-build-status-hook

That way if I update master before starting on a new feature, I get a notification if the tip of master is broken (or still building).

Re:Safer branching by eridius on Thursday October 06, 2016 @02:25PM (#12654798)
What would be nice is automatically attaching git-notes to commits indicating whether or not they passed CI. That said, I haven't looked into git-notes for a few years, so I'm not sure if they ever made it easy to sync them without a bunch of manual configuration.