Use consistent path for downloadable satre.xlsx spreadsheet #295
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
✅ Checklist
☑️ Maintainers' checklist
Currently we use the Sphinx
:download:
role to make the satre.xlsx spreadsheet available, but this results in a random hash being included in the published path. This is annoying since we can't link directly to the spreadsheet.This PR is a workaround so that satre.xlsx is always in the base directory, without a prefix, so in future we can use
https://satre-specification.readthedocs.io/en/stable/satre.xlsx
instead of
https://satre-specification.readthedocs.io/en/stable/_downloads/<random-hash-which-changes-every-release>/satre.xlsx
🌂 Related issues
🙋 Acknowledging contributors