* Log `git checkout` and expose to users
* Use `setup_env` and record for `git clone`
* Use LocalEnvironment to record VCS commands in the build
* Split LocalEnvironment into LocalBuildEnvironment and LocalEnvironment
* LocalEnvironment
* env fix
* Run VCS command in the proper environment
* Define env
* Proper env variables
* Pass proper env variables when running VCS commands
* warn_only in status
* Record command when inside a BuildEnvironment
* Remove --quiet options
* Do not record ``warn_only`` commands
* Refactor
* Add warn_only to other VCS
* Remove `update_imported_docs` and use UpdateDocsTask
* Hack the Environment logs to avoid fails because no version
* Abstraction for UpdateDocsTask and SyncRepositoryTask
These are two separated tasks that share some code by inheriting from
SyncRepositoryMixin.
The final goal (as ``core.views.hooks._build_url`` is *DEPRECATED*) is
to finally remove the SyncRepositoryTask and merge that code into
UpdateDocsTask.
* Allow to not record specific command
Either `record=False` or `warn_only=True` commands are not
recorded. This attributes can be set at initialization time or when
calling the `run()` method.
* Proper use of `record`, `warn_only` and the new `force_success`
* Use record_as_success instead of force_success
We need the real exit_code for some command since there are decisions
based on that code, but we want to record it as success.
So, the fake exit_code is saved in the database but the real exit_code
is used in the whole flow of the building process.
* Replace force_success to record_as_success in calls
* Lint
* Fix docs styling
* Remove unnecessary initializing variables
As MkDocs doesn't support automatic PDF generation, selecting the
Mkdocs documentation type means that you can't enable PDF builds. Where
Mkdocs or markdown is mentioned in the docs, this is more explicit.