load statements are not eligible for "implicit rule names" (#260)

"If a build file contains exactly one unnamed rule" currently matches the load statement in the following:

```
load("//foo", "some_rule")

some_rule(
    name = "bar",
)
```

This is clearly not the intent of the implicit rule name case, so tweak it accordingly.
2 files changed
tree: cb99b4e6a33c8ab4041604eb4ea21919d508abd8
  1. .bazelci/
  2. api_proto/
  3. build/
  4. build_proto/
  5. buildifier/
  6. buildifier2/
  7. buildozer/
  8. config/
  9. deps_proto/
  10. differ/
  11. edit/
  12. extra_actions_base_proto/
  13. file/
  14. generatetables/
  15. lang/
  16. tables/
  17. unused_deps/
  18. wspace/
  19. .gitignore
  20. BUILD.bazel
  21. CONTRIBUTING.md
  22. CONTRIBUTORS
  23. LICENSE
  24. README.md
  25. status.sh
  26. WORKSPACE
README.md

Buildtools for bazel

This repository contains developer tools for working with Google's bazel buildtool.

Build status

Setup

See instructions in each tool's directory.