ci: mark workspace safe for git so mike can deploy docs in-container#91
Merged
Conversation
The deploy-docs workflows run inside cubertgmbh/cuvis_pyil and check out the
repo as a different owner than the container user, so git refused the
workspace ("fatal: not in a git directory") at the "Configure git for mike"
step and the gh-pages deploy never ran. Add
`git config --global --add safe.directory "$GITHUB_WORKSPACE"` right after
checkout in both deploy workflows, matching the sister repos.
birkholz-cubert
approved these changes
Jun 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem
The docs deploy that ran after #88 merged to
mainfailed at the Configure git for mike step withfatal: not in a git directory(run 26879965556). The deploy workflows run inside thecubertgmbh/cuvis_pyilcontainer, whereactions/checkoutleaves the workspace owned by a different user than the container runs as, so git refuses to operate on it. As a resultgh-pagesis never created and the site never publishes.Fix
Add
git config --global --add safe.directory "$GITHUB_WORKSPACE"right after checkout in both deploy workflows (nightly + versioned), matching the sister repos.docs-check.ymlruns onlymkdocs build(no git/mike), so it doesn't need it.After merge
The push to
mainre-runs the nightly deploy, which createsgh-pagesand publishes the site. A maintainer then switches Settings → Pages → Deploy from branch:gh-pages.