Clarify meaning of "hook environments" about pre-commit.com HOT 9 CLOSED

patches welcome!

from pre-commit.com.

that means they're already up to date and installed then (it's idempotent).

here's some output you might see if they weren't already installed:

$ pre-commit install --install-hooks
pre-commit installed at .git/hooks/pre-commit
[INFO] Initializing environment for https://gitlab.com/pycqa/flake8.
[INFO] Installing environment for https://gitlab.com/pycqa/flake8.
[INFO] Once installed this environment will be reused.
[INFO] This may take a few minutes...

from pre-commit.com.

Thanks... can you clarify what you mean by "environment"? Is that the language?

from pre-commit.com.

or virtual environment?

from pre-commit.com.

It depends on the language, for python it's virtualenvs, for go it's a binary built from a temporary gopath. It's kind of intentionally ambiguous in the docs so it doesn't need to enumerate the many different types of installs that can occur.

from pre-commit.com.

OK. Need to have a look into it and maybe quickly update the doc...

from pre-commit.com.

@asottile

It's kind of intentionally ambiguous in the docs so it doesn't need to enumerate the many different types of installs that can occur.

Is that in the interest of saving space in the top-level documentation, or not having to maintain documentation of a moving target?

from pre-commit.com.

It's because it would be duplicated with the language-specific docs and prohibitively verbose and unnecessary to enumerate

from pre-commit.com.

Gotcha. Well, I understand the problem, but I'd gently suggest that directing the reader to the language specific docs would be better than intentional vagueness in this case.

from pre-commit.com.