bazelbuild / bazelbuild/remote-apis

use github.com/googleapis/googleapis directly

Open
#125 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
445
Forks
141
PR merge metrics
No merged PRs in 30d

Description

I am integrating this repository into my own Bazel project.

I am already using `github.com/googleapis/googleapis` as the `@googleapis` repository (the canonical one), which collides with the definition of the `@googleapis` repository for which a `BUILD.googleapis` file is vendored in `external` (the vendored).

I looked through the differences. I noticed that mainly the `@googleapis` vendored here ships with `cc_grpc_library` targets on top of a few things that the canonical repo already has.

It would probably be best to consolidate the two. Would like to open the discussion a bit.

Contributor guide

Open the contributing guide

Research direction

Start by comparing the canonical github.com/googleapis/googleapis repository with the vendored external/BUILD.googleapis definition, focusing on the cc_grpc_library targets and other differences mentioned in the issue. Determine the maintainers' preferred consolidation approach; done would mean an agreed resolution for the @googleapis repository collision.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
build-system
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.