Fix docs at index being outdated #1331
Conversation
Rough steps, committing just the needed files in the end:
```sh
mike deploy --update-aliases --alias-type=redirect latest index
find index -name '*.html' -exec sed -i 's:\.\./latest:latest:g' {} +
for f in index/{,*/,*/*/}*.html; do git mv "$f" "${f#index/}"; done
```
|
Branch gh-pages will be overridden on next run of the regular docs job. |
|
Do you mean manual commits would be lost? If you mean the contents of the files, then these ones are not being updated by the CI, and If you have another idea for a solution, I'm all for it, but I know this will work (fully tested on my fork, including tagging a new release after this is merged) and really don't see any other way. |
|
I'm not against this solution, I just have concerns that your work will be lost. I'm not sure, but my understanding was: documentation source is the main branch (docs directory). CI job creates all needed files and pushes them to gh-pages branch. Some file manipulation on gh-pages branch manually will be overridden (I think the job will do some kind of git push --force if there are some conflicts). We can try to merge it and we can then observe what happens in the future. |
|
Yeah that happens to files that are under |
|
Redirect works fine: the link in the repo sidebar (https://0xerr0r.github.io/blocky/) now redirects to, ATM, https://0xerr0r.github.io/blocky/v0.23/ |
/configurationwill redirect to/latest/configurationwhich actually gets updated by the CI.Fix #1329