<NME> Project.toml
<BEF> [deps]
Documenter = "e30172f5-a6a5-5a46-863b-614d45cd2de4"
DocumenterTools = "35a29f4d-8980-5a13-9543-d66fff28ecb8"
libsass_jll = "47bcb7c8-5119-555a-9eeb-0afcc36cd728"

[compat]
DocumenterTools = "=0.1.12"
libsass_jll = "~3.6"

<MSG> Use DocumenterTools as a dev dep in docs/ (#1876)

* Use DocumenterTools as a dev dep in docs/

This does a few things:

1. The source links to the DocumenterTools docstrings do not work right
now because we Pkg.add it, but we need the source files to be located in
a Git repository for gitremote to determine the remote repository. We
can work around that by making it a Pkg.develop dependency instead.

2. If we add it as a dev dependency, we can use unreleased branches
which declare support for newer Documenter versions, and so we can use
the -DEV versions in the Documenter repository now. However, this
requires checking out a particular branch (or tag) of DocumenterTools.
Pkg.develop can not be used for this since it does not know how to check
out specific branches, and will fail as it tries to check out master
(which will not be compatible with e.g. 0.28.0-DEV).

3. Since adding it as a local dev dependency is a slightly non-trivial,
this creates a separate docs/instantiate.jl script which does the
necessary cloning and Pkg environment manipulations, just to make life
easier locally and in the CI config.

Co-authored-by: Fredrik Ekre <c9fed246bcfe477bbc1f7db2e4d8c6d92b09bd82@gmail.com>
<DFF> @@ -4,5 +4,4 @@ DocumenterTools = "35a29f4d-8980-5a13-9543-d66fff28ecb8"
 libsass_jll = "47bcb7c8-5119-555a-9eeb-0afcc36cd728"
 
 [compat]
-DocumenterTools = "=0.1.12"
 libsass_jll = "~3.6"

Use DocumenterTools as a dev dep in docs/ (#1876)