- edited description
Adopt sphinx-issues, drop CHANGES.rst
We can add sphinx-issues to the docs import, then use :issue:
and :pr:
to link back to Bitbucket rather than having to create a link reference for every single line in docs/changes.rst
.
This possibly doesn’t work for CHANGES.rst because it would be rendered by Bitbucket with whichever sphinx options they have in use. But I can’t see any reason to keep the file, so we’ve probably just been wasting our time duplicating it there and in docs. We need one or the other, and we have the docs version.
Might make my copying of the changes for the website version more of a challenge, but I’m sure I’ll get over it.
Comments (8)
-
reporter -
reporter Added sphinx-issues. Refs
#820→ <<cset a257f2b26b11>>
-
reporter See if issue link works. Refs
#820→ <<cset c974d1826916>>
-
reporter Updating docs requirements.txt. Refs
#820→ <<cset 2774cf9d5a6f>>
-
reporter Converted all remaining issue links. Refs
#820→ <<cset 2649ac722588>>
-
reporter Deleted CHANGES.rst, added ref
#820to changes, removed sphinx-issues from general requirements.txt→ <<cset 9959114c8498>>
-
reporter Asking codacy to ignore constants that should be uppercase, but lower case is specified by sphinx-issues. Refs
#820→ <<cset c4a0cae54e84>>
-
reporter - changed status to resolved
- Log in to comment