We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The last thing to do before registering v0.6.0 in the General registry is to update the documentation.
@Evizero Looks like this repository haven't set up auto-deployment CI for documentation, right? Can you add a deploy key and a secret key (with name DOCUMENTER_KEY) following the instruction of https://juliadocs.github.io/Documenter.jl/stable/man/hosting/#travis-ssh-1 I plan to set the documentation via Github action
DOCUMENTER_KEY
The text was updated successfully, but these errors were encountered:
If the docs are still the way I did them then they don't really work in a CI environment
Sorry, something went wrong.
I'm modifying the docs to adapt the current Documenter system; the idea is to rewrite them using DemoCards.jl, which is CI friendly :P
Hmmm.. May I tag v0.6.0 in spite of the not updated documents? I need this package registered/tagged for reproduction consideration.
sure
Evizero
No branches or pull requests
The last thing to do before registering v0.6.0 in the General registry is to update the documentation.
@Evizero Looks like this repository haven't set up auto-deployment CI for documentation, right? Can you add a deploy key and a secret key (with name
DOCUMENTER_KEY
) following the instruction of https://juliadocs.github.io/Documenter.jl/stable/man/hosting/#travis-ssh-1 I plan to set the documentation via Github actionThe text was updated successfully, but these errors were encountered: