Skip to content

Idea - Leverage pip.dep for the coverage tooling #3902

Description

@aignas

This is just a thought and it might not work but maybe it would.

  1. Define a pip.dep with an extra alias to have an executable filegroup which is what the toolchain requires. This probably requires pip.dep to accept extra args.
  2. If users attempt to run bazel coverage they would get an error asking them to include the coverage in the requirements.txt.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions