chore: remove generated docs (#673)

Stardoc is a pain in the butt because of its transitive deps. It also
makes a bad contributor experience when a minor .bzl fix results in a
red PR forcing you to run stardoc on your machine.

The next release will have docs on the BCR instead.

---------

Co-authored-by: aspect-marvin[bot] <[email protected]>

Author: alexeagle

.gitattributes

@@ -1,7 +1,3 @@
-docs/*.md linguist-generated=true
-docs/migrating.md linguist-generated=false
-docs/virtual_deps.md linguist-generated=false
-
 # Configuration for 'git archive'
 # see https://git-scm.com/docs/git-archive/2.40.0#ATTRIBUTES
 # Don't include examples in the distribution artifact, just to reduce size

.pre-commit-config.yaml

@@ -34,12 +34,6 @@ repos:
 
   - repo: local
     hooks:
-      - id: check-docs
-        name: Update docs
-        entry: /usr/bin/env bazel run //docs:update
-        language: script
-        require_serial: true
-
       - id: check-requirements-lock
         name: Update requirements lock
         # Note that we use a nested shell to discard $@, which is the file list

.prettierignore

@@ -1 +0,0 @@
-docs/*.md

README.md

@@ -71,19 +71,7 @@ In any ancestor `BUILD` file of the Python code, add these lines to instruct [Ga
 
 # Public API
 
-## Executables
-
-- [py_binary](docs/py_binary.md) an executable Python program, used with `bazel run` or as a tool.
-- [py_test](docs/py_test.md) a Python program that executes a test runner such as `unittest` or `pytest`, to be used with `bazel test`.
-- [py_venv](docs/venv.md) create a virtualenv for a `py_binary` or `py_test` target for use outside Bazel, such as in an editor/IDE.
-
-## Packaging
-
-- [py_pex_binary](docs/pex.md) Create a zip file containing a full Python application.
-
-## Packages
-
-- [py_library](docs/py_library.md) a unit of Python code, used as a dependency of other rules.
+See https://registry.bazel.build/docs/aspect_rules_py
 
 # Telemetry & privacy policy