delta/python-packages/sphinx-git.git/.github, branch v6.2.0

Continuous integration: resolve docutils installation step build failures (#11331)

2023-04-16T13:05:09+00:00

* continuous integration: add comment explaining PYTHONWARNINGS env var to main unit test workflow

* continuous integration: unit test workflow: report-but-do-not-fail
  when warnings about pkg_resources deprecation are encountered during
  docutils dependency installation

* continuous integration: unit test workflow: instead of reducing the
  severity of all DeprecationWarnings during docutils (non-dev)
  installation, apply two message filters - one each for the warnings
  encountered so far

* continuous integration: unit test workflow: add 'module' and 'line'
  fields for warning filters

Ref:
https://docs.python.org/3/library/warnings.html#describing-warning-filters


---------

Co-authored-by: Jean-François B <2589111+jfbu@users.noreply.github.com>

Enable 'nit-picky mode' for Sphinx's documentation

2023-04-06T22:11:39+00:00

Fix several reference errors throughout the documentation and set
``nitpick_ignore`` in ``doc/conf.py``.

Resolve lint errors from Ruff 0.0.261

2023-04-05T13:19:43+00:00

Run Ruff linting with a known-to-work version

2023-03-31T16:52:29+00:00

This means that CI tests will only fail if the 'known good' version
fails. If the latest version of Ruff fails, perhaps due to new
checks, CI will not fail overall, but the failures from the latest
version will be reported.

Pin to ruff==0.0.259 (provisory)

2023-03-31T15:18:29+00:00

This is because I would like CI to succeed for a while in order to merge
some LaTeX patch.

Provis. ignore onerror depr. warn when install. DocUtils with 3.12-dev

2023-03-26T21:52:55+00:00

Properly quote a string value in ``transifex.yml``

2023-03-15T15:47:25+00:00

Update translations workflow for new ``tx`` client

2023-03-15T15:45:36+00:00

Simplify coverage workflow reporting

2023-02-15T05:24:51+00:00

``PYTHONDEVMODE`` and ``PYTHONWARNDEFAULTENCODING`` are used in the
main tests, remove from the coverage workflow.

Ignore ``coverage.py`` warnings

2023-02-15T05:14:44+00:00