I’ve recently moved some of my repos into a new GitHub organisation. After merging a pull request today, I realised that the documentation is no longer deployed:
┌ Info: Deployment criteria for deploying devbranch build from GitHub Actions:
│ - ✘ ENV["GITHUB_REPOSITORY"]="JuliaTrustworthyAI/CounterfactualExplanations.jl" occurs in repo="github.com/juliatrustworthyai/CounterfactualExplanations.jl.git"
│ - ✔ ENV["GITHUB_EVENT_NAME"]="push" is "push", "workflow_dispatch" or "schedule"
│ - ✔ ENV["GITHUB_REF"] matches devbranch="main"
│ - ✔ ENV["GITHUB_ACTOR"] exists and is non-empty
│ - ✔ ENV["DOCUMENTER_KEY"] exists and is non-empty
└ Deploying: ✘
This was never an issue when the repo was still hosted on my own account. I’m not sure how to make sure that this environment variable is available. Do I just hard-code it somewhere into the CI.yml?
Thanks @kellertuer, good spot! I think the .git should be fine, base on docs, but it seems that the repo argument is case-sensitive. Just tried it for a different repo, for which the same error previously occurred
- ✘ ENV["GITHUB_REPOSITORY"]="JuliaTrustworthyAI/ConformalPrediction.jl" occurs in repo="github.com/juliatrustworthyai/ConformalPrediction.jl"
- ✔ ENV["GITHUB_EVENT_NAME"]="push" is "push", "workflow_dispatch" or "schedule"
- ✔ ENV["GITHUB_REF"] matches devbranch="main"
- ✔ ENV["GITHUB_ACTOR"] exists and is non-empty
- ✔ ENV["GITHUB_TOKEN"] exists and is non-empty
Deployment criteria for deploying devbranch build from GitHub Actions:
- ✔ ENV["GITHUB_REPOSITORY"]="JuliaTrustworthyAI/ConformalPrediction.jl" occurs in repo="github.com/JuliaTrustworthyAI/ConformalPrediction.jl"
- ✔ ENV["GITHUB_EVENT_NAME"]="push" is "push", "workflow_dispatch" or "schedule"
- ✔ ENV["GITHUB_REF"] matches devbranch="main"
- ✔ ENV["GITHUB_ACTOR"] exists and is non-empty
- ✔ ENV["GITHUB_TOKEN"] exists and is non-empty