Comments (17)
Remove the ".git" in repo
?
from documenter.jl.
I'd try deleting all keys and secrets from both repos and start from scratch with DocumenterTools.genkeys
from documenter.jl.
It finally works. Thanks for your help!
from documenter.jl.
My pleasure! It's the least I can do as a small Thank You for JuliaMono!
from documenter.jl.
Thank! Yes, the path looks better now, but although this link looks valid
https://github.com/JuliaGraphics/Luxor.jl/actions/runs/7544837907/job/20539088958#step:7:508
there's still an access error. Perhaps the secret keys aren't correctly set.
from documenter.jl.
Yeah, that looks like the secrets aren’t set up right in the two repositories
from documenter.jl.
I’ll try and do them again tomorrow. It’s by far the worst aspect of working with Julia… 😂
from documenter.jl.
I did the process again:
Error is:
remote: Permission to JuliaGraphics/LuxorManual.git denied to github-actions[bot].
[507](https://github.com/JuliaGraphics/Luxor.jl/actions/runs/7544837907/job/20564991449#step:7:508)
fatal: unable to access 'https://github.com/JuliaGraphics/LuxorManual.git/': The requested URL returned error: 403
[508](https://github.com/JuliaGraphics/Luxor.jl/actions/runs/7544837907/job/20564991449#step:7:509)
┌ Error: Failed to push:
[509](https://github.com/JuliaGraphics/Luxor.jl/actions/runs/7544837907/job/20564991449#step:7:510)
│ exception =
[510](https://github.com/JuliaGraphics/Luxor.jl/actions/runs/7544837907/job/20564991449#step:7:511)
│ failed process: Process(setenv(`/home/runner/.julia/artifacts/5d776960702ec06ebaac2a94fd96a1c44e8cb04a/bin/git push -fq upstream HEAD:gh-pages`,
make.jl
code is:
repo = "JuliaGraphics/LuxorManual"
withenv("GITHUB_REPOSITORY" => repo) do
deploydocs(
repo = repo,
target = "build",
push_preview = true,
forcepush = true,
)
end
So I think the documented procedure isn't working ... ?
from documenter.jl.
@mortenpi Does my screenshot above look correct? It’s my best guess based on the current documentation…
from documenter.jl.
Don't think you have DOCUMENTER_KEY
set up right, since it's trying to use GITHUB_TOKEN
: https://github.com/JuliaGraphics/Luxor.jl/actions/runs/7544837907/job/20539088958#step:7:133 (also #2165).
Any reason you're trying to configure an environment, rather than just setting up a global secret? I assume the workflow just doesn't have access to the environment.. I think you have to explicitly tell a workflow to use an environment.
- https://docs.github.com/en/actions/deployment/about-deployments/deploying-with-github-actions
- https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment
from documenter.jl.
Any reason you're trying to configure an environment
I have no idea 😀I think the output of generate_keys
said to create an environment variable so I added it. Did I add it to the wrong place?
from documenter.jl.
Should be in "Secrets and variables"
from documenter.jl.
Should be in "Secrets and variables"
Thanks... I'm obviously the only one to be confused by this but I don't get it at all :(
The Secrets tab has 3 secrets panels - the Documenter docs say "Add the DOCUMENTER_KEY secret to the "source" repository". The genkeys()
text says "add a secure environment variable" and the Variables tab has 3 variables panels...
rather than just setting up a global secret?
I can't see any 'global secrets? Just 'Environment Secrets', 'Repository Secrets' and 'Organisation Secrets'.
I'll try copying "the secure environment variable named 'DOCUMENTER_KEY'" to the "Actions secrets and variables/Environment secrets" panel and see if that works.
Thanks for the help though! :)
from documenter.jl.
I'm confused about this myself. I have the impression that the Github UI is somewhat redundant: the same "secrets" are accessible in multiple places, as far as I can tell. They've also changed the UI over the last year or so. At some point, we should change genkeys
to give less ambiguous instructions.
But basically, the SSH key goes into Security > Deploy Keys
And the DOCUMENTER_KEY
variable goes into Secrets and Variables > Actions > Repository Secrets
Those screenshots are from a standard setup where the documentation is deployed to the same repository. I guess for out-of-repo deployment those two settings are just in different repositories, but otherwise it's the same. I haven't set up out-of-repo deployment myself, though.
from documenter.jl.
Thanks, @goerz - the pictures are worth a thousand words. I think I have set the keys and secrets correctly now. As you say I think Github must have changed the UI recently...
The error now is :
ssh: Could not resolve hostname juliagraphics: Temporary failure in name resolution
fatal: Could not read from remote repository.
so I'll try again later this weekend to see if this "temporary failure" really is temporary, or is the next obstacle for me.
from documenter.jl.
The line repo = "JuliaGraphics/LuxorManual"
in your make.jl
is wrong: that should probably be repo = "github.com/JuliaGraphics/LuxorManual.git"
, according to the documentation.
from documenter.jl.
Thanks! I’ll try that again (it didn’t work before, but perhaps it will work better with the new secrets…).
from documenter.jl.
Related Issues (20)
- Switching versions resets to the default page HOT 3
- LoadError: `makedocs` encountered an error [:missing_docs] -- terminating build before rendering. HOT 7
- Links to collapsed pages end up off-screen
- Documenter might not be expanding the example blocks in docstrings HOT 2
- Handling of ANSI foreground/background inversion is incorrect HOT 3
- Use AnnotatedIOBuffer + StyledStrings for handling ANSI codes. HOT 2
- ERROR: LoadError: PCRE compilation error: regular expression is too large HOT 9
- Cross reference between modules HOT 3
- Use mathml as an alternative `mathengine` HOT 3
- Anchors for admonitions
- How to create custom badges HOT 2
- Cannot find level-three cross-references HOT 6
- Got a `If you are seeing this warning/error after upgrading Documenter and this used to work`
- Doctest fix versus exceptions
- Allow setting a global `DocTestSetup` block for all `.md` files in one place
- Make search_index a JSON file
- Alternative admonition syntax?
- Support for external parsers like CommonMark HOT 2
- Profiling docs build times HOT 3
- Not Matching Versions for Subpackage Version Tags HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from documenter.jl.