Further, it doesn't appear that our own API allows you to set specific roles/groups/people on those protected branches anyway....

Looked into it quickly....

@rspeicher Thanks, addressed in 5618122!

Weird, it works for me, but yeah --format='something' works too and is simpler, I'll change that.

Yes, describe '.get' do doesn't output to stdout...

Yes it's basically a stub.

Actually, have_blob should now be called on a Rugged::Repository since I'm using Rugged::Repository#blob_at.

Actually I changed .run_git to return [cmd_output, cmd_status] so we don't need this param anymore.

I think the call was ambiguous without that.

https://github.com/bbatsov/rubocop/blob/ce6483c8f83691837519ab0a4f996a74f9de11dc/lib/rubocop/cop/style/special_global_vars.rb

@rymai Couple more questions. 👍

paths might be more in line with the actual Git documentation/usage.

This argument doesn't work for me locally -- it can be either --format='something' or --pretty='something', and both seem to be functionally identi...

Thes

Any reason we shouldn't add this metadata to the top-level describe?

How do these actually silence the output? Is it basically a stub?

What's the benefit of using .for instead of expect(master.target)?

Are we not using output until !86?

Parentheses for the raise call are a bit unusual.