RPC's for 'Git smart HTTP' POST requests

~Conversation: gitaly#219 (closed)

For https://gitlab.com/gitlab-org/gitaly/issues/92

added 1 commit

• c9065a6c - RPC's for 'Git smart HTTP' POST requests

Compare with previous version

added 1 commit

• f0b49b25 - RPC's for 'Git smart HTTP' POST requests

Compare with previous version

assigned to @andrewn

mentioned in issue gitaly#122 (closed)

mentioned in issue gitaly#125 (closed)

mentioned in issue gitaly#131 (closed)

I will rebase this to make it mergeable.

@ahmadsherif since you will be working on this, any thoughts on the proto proposed here?

@jacobvosmaer-gitlab Nope, I think they're good.

added 5 commits

• f0b49b25...50e41c92 - 4 commits from branch master
• 4e745ae3 - RPC's for 'Git smart HTTP' POST requests

Compare with previous version

enabled an automatic merge when the pipeline for 4e745ae3 succeeds

added 1 commit

• ec6bd38c - Print proto files to debug CI build changes

Compare with previous version

Something weird is going on where the google .pb.go files generated in CI differ from what I generated locally and committed. This breaks the build. Added a debug statement to see if it is about file order.

added 1 commit

• 189f4ead - Contributions must use Go 1.8 to generate libs

Compare with previous version

enabled an automatic merge when the pipeline for 189f4ead succeeds

I found the source of the problem (Go 1.8 has different gzip output than Go 1.7, my local machine has Go 1.8, CI was using Go 1.7). Added 189f4ead to document a workaround (contributors must use Go 1.8).

merged

mentioned in commit 25d009eb

mentioned in issue gitaly#219 (closed)

mentioned in issue gitaly#353