Closed henri-hulski closed 2 years ago
After deleting the stale branches this issue was solved. Now I get the following error:
with:
branch: gh-pages
folder: docs/build
token: ***
clean: true
force: true
env:
pythonLocation: /opt/hostedtoolcache/Python/[3](https://github.com/stephenmcd/mezzanine/runs/6443590576?check_suite_focus=true#step:9:3).9.12/x6[4](https://github.com/stephenmcd/mezzanine/runs/6443590576?check_suite_focus=true#step:9:4)
LD_LIBRARY_PATH: /opt/hostedtoolcache/Python/3.9.12/x64/lib
RELEASE_TAG: v6.0.0
đź’– Support: https://github.com/sponsors/JamesIves
đź“Ł Maintained by James Ives: https://jamesiv.es
🚀 Getting Started Guide: https://github.com/JamesIves/github-pages-deploy-action
âť“ Discussions / Q&A: https://github.com/JamesIves/github-pages-deploy-action/discussions
🔧 Report a Bug: https://github.com/JamesIves/github-pages-deploy-action/issues
Checking configuration and starting deployment… 🚦
Deploying using Deploy Token… 🔑
Configuring git…
/usr/bin/git config --global --add safe.directory /home/runner/work/mezzanine/mezzanine
/usr/bin/git config user.name henri-hulski
/usr/bin/git config user.email henri.hulski@gazeta.pl
/usr/bin/git config core.ignorecase false
/usr/bin/git config --local --unset-all http.https://github.com/.extraheader
/usr/bin/git remote rm origin
/usr/bin/git remote add origin ***github.com/stephenmcd/mezzanine.git
Git configured… 🔧
Starting to commit changes…
/usr/bin/git ls-remote --heads ***github.com/stephenmcd/mezzanine.git refs/heads/gh-pages
39cd036[5](https://github.com/stephenmcd/mezzanine/runs/6443590576?check_suite_focus=true#step:9:5)8b3d98[6](https://github.com/stephenmcd/mezzanine/runs/6443590576?check_suite_focus=true#step:9:6)[7](https://github.com/stephenmcd/mezzanine/runs/6443590576?check_suite_focus=true#step:9:7)a1f42f2095[8](https://github.com/stephenmcd/mezzanine/runs/6443590576?check_suite_focus=true#step:9:8)f22f17cb1d[9](https://github.com/stephenmcd/mezzanine/runs/6443590576?check_suite_focus=true#step:9:9)9c refs/heads/gh-pages
Creating worktree…
/usr/bin/git fetch --no-recurse-submodules --depth=1 origin gh-pages
From https://github.com/stephenmcd/mezzanine
* branch gh-pages -> FETCH_HEAD
* [new branch] gh-pages -> origin/gh-pages
/usr/bin/git worktree add --no-checkout --detach github-pages-deploy-action-temp-deployment-folder
Preparing worktree (detached HEAD 567c96d2)
/usr/bin/git checkout -B gh-pages origin/gh-pages
Previous HEAD position was 567c96d2 chore: update workflow
Switched to a new branch 'gh-pages'
branch 'gh-pages' set up to track 'origin/gh-pages'.
/usr/bin/chmod -R +rw /home/runner/work/mezzanine/mezzanine/docs/build
/usr/bin/rsync -q -av --checksum --progress /home/runner/work/mezzanine/mezzanine/docs/build/. github-pages-deploy-action-temp-deployment-folder --delete --exclude CNAME --exclude .ssh --exclude .git --exclude .github
Checking if there are files to commit…
/usr/bin/git add --all .
error: insufficient permission for adding an object to repository database /home/runner/work/mezzanine/mezzanine/.git/objects
error: .doctrees/multi-tenancy.doctree: failed to insert into database
error: unable to index file '.doctrees/multi-tenancy.doctree'
fatal: adding files failed
Running post deployment cleanup jobs… 🗑️
/usr/bin/git checkout -B github-pages-deploy-action/2rbdh7u29
Switched to a new branch 'github-pages-deploy-action/2rbdh7u29'
M index.html
/usr/bin/chmod -R +rw github-pages-deploy-action-temp-deployment-folder
/usr/bin/git worktree remove github-pages-deploy-action-temp-deployment-folder --force
Error: The deploy step encountered an error: The process '/usr/bin/git' failed with exit code [12](https://github.com/stephenmcd/mezzanine/runs/6443590576?check_suite_focus=true#step:9:12)8 ❌
Notice: Deployment failed! ❌
Maybe it would help to add .gitignore
with *.doctree
and doctrees
.
Sorry for the late response time on this. You could add this to your repos .gitignore
file before the deployment job runs and I think and it should have the same effect.
Describe the bug
Deployment fails with permission issues when trying to remove origin.
Logs
Workflow
Additional Comments
The release step succeeded, so there shouldn't be a problem with the GITHUB_TOKEN. I'm using the same setup with stephenmcd/cartridge, where it works fine. Maybe a problem with the initial gh-pages branch, but when I removed it I got the same error.