adityak368
Docs deployment error
The github action which deploys a release appears to have a auth problem when deploying the documentation. See the output for the 3.3 release.
I've never used an action for this. I use this: https://github.com/facelessuser/pymdown-extensions/blob/master/.github/workflows/deploy.yml#L30. Seems to work still as I released 10 days ago.
I didn't use that because we are using an org setup, where the built site is deployed to the master branch of a different repo rather than the gh-pages branch of the same repo. I'm assuming the auth issue is related to crossing the two repos. I thought I had done everything correctly, but apparently not. For the record, this was the first test if it all, so it has never worked.
When I did this I followed these instructions and set up the deploy key as instructed here with the private key saved to this repo (as a secret named PAGES_DEPLOY_KEY) and the public key saved to the Python-Markdown/Python-Markdown.github.io repo (as a deploy_key). I'm assuming I messed something up with that.
Maybe I need to save the secret to the organization rather than the repo? That way the other repo would also have access. I'm guessing here.
See Manually running a workflow, which could be handy for testing purposes.
When a workflow is configured to run on the
workflow_dispatchevent, you can run the workflow using the REST API or from the Actions tab on GitHub.
See also workflow_dispatch.
As a reminder to myself, when I released 3.3.1 yesterday, I had done nothing to address this issue and the same error occurred. I expected as much, but didn't want to delay getting that fix out so went forward and manually deployed the docs.
This may be resolved with github-action-push-to-another-repository, which has comprehensive documentation (including all sorts of troubleshooting tips). Also copy_file_to_another_repo_action is a simpler action. Both are implemented as shell scripts, which could be helpful in developing our own solution around mkdocs gh-deploy. Or we could use one of them directly.
Hmm, I just discovered that Python-Markdown/Python-Markdown.github.io did not have any deploy keys. Anyway, I just generated a new public/private pair and saved them to the correct locations. We'll see if that resolves it with the next release.