Remove unused visibility specs (last referenced in codebase over 391 days ago)
You may notice rules being explicitly set to visibility = ["//visibility:private"] even with no default_visibility being defined in the BUILD file. Please see go/scheuklappen#explicit-private for an explanation.
If you receive a CL that sets every rule in a package to private and would like to delete the package instead, please REVERT the CL and create a follow-up CL removing the directory yourself. Scheuklappen does not directly support this.
Only private by automation, not intent. Owner may accept CLs adding visibility.
go/scheuklappen for more information on this change.
See go/scheuklappen-lsc for more information on why you've received this change and why it is important.
This CL looks good? Just LGTM and Approve it!
This CL doesn’t look good? This is what you can do:
Revert this CL, by replying "REVERT: "
File a bug under go/scheuklappen-bug for category BuildVisibility if there's an issue with the CL content.
File a bug under go/rosie-bug if there's an issue with how the CL was managed.
For all other issues such as the formatting of the CL, please file a bug under
go/clrobot-bug.
Revert this CL and not get a CL that cleans up these paths in the future by
replying "BLOCKLIST: ". This is not reversible! We recommend to
opt out the respective paths in your CL Robot configuration instead:
go/clrobot-opt-out.
This CL was generated by CL Robot - a tool that cleans up code findings
(go/clrobot). The affected code paths have been enabled for CL Robot in //depot/google3/METADATA by
following go/clrobot#how-to-opt-in. Anything wrong with the signup? File a bug
at go/clrobot-bug.
Remove unused visibility specs (last referenced in codebase over 391 days ago)
visibility = ["//visibility:private"]even with nodefault_visibilitybeing defined in theBUILDfile. Please see go/scheuklappen#explicit-private for an explanation.See go/scheuklappen-lsc for more information on why you've received this change and why it is important.
This CL looks good? Just LGTM and Approve it! This CL doesn’t look good? This is what you can do:
This CL was generated by CL Robot - a tool that cleans up code findings (go/clrobot). The affected code paths have been enabled for CL Robot in //depot/google3/METADATA by following go/clrobot#how-to-opt-in. Anything wrong with the signup? File a bug at go/clrobot-bug.
codehealth