Labels

• bazel 1.0

  bazel 1.0

  Issues that the team wants to fix before Bazel 1.0

• category: code coverage

  category: code coverage

  Issues related to code coverage (collection, profile merging, generation, etc.)

• category: core rules

  category: core rules

• category: toolchains

  category: toolchains

• cla: no

  cla: no

• cla: yes

  cla: yes

• community-reviewed

  community-reviewed

  Reviewed by a trusted community contributor

• External discussion

  External discussion

  This issue/PR is being discussed elsewhere. Probably bazelbuild/bazel

• Good Starter Bug

  Good Starter Bug

  Good bug to start getting involved in rules_cc!

• P0

  P0

  This is an emergency and more important than other current work. (Assignee required)

• P1

  P1

  I'll work on this now. (Assignee required)

• P2

  P2

  We'll consider working on this in future. (Assignee optional)

• P3

  P3

  We're not considering working on this, but happy to review a PR. (No assignee)

• P4

  P4

  This is either out of scope or we don't have bandwidth to review a PR. (No assignee)

• platform: darwin

  platform: darwin

• platform: linux

  platform: linux

• platform: windows

  platform: windows

• type: bug

  type: bug

  Something that should be working isn't working

• type: documentation

  type: documentation

  Request to document existing feature

• type: feature request

  type: feature request

  Request for new, generally useful functionality that is missing

• type: internal cleanup

  type: internal cleanup

  Does not directly address a feature request or a bug report, but improves project hygiene

• type: support /not a bug

  type: support /not a bug

  This issue is not a bug per se, more like a question. We prefer these to be asked on StackOverflow.

• under investigation

  under investigation

  Issue couldn't be triaged, more data or investigation is needed

• untriaged

  untriaged

  Team member has to triage this issue - assign priority, type, and owner (if possible).