Skip to content

fix: use deploy key instead of token for gh-pages deployment - #483

Merged
leandrumartin merged 2 commits into
oss-slu:developfrom
sakshar2303:fix/use-deploy-key-for-gh-pages
May 25, 2026
Merged

fix: use deploy key instead of token for gh-pages deployment#483
leandrumartin merged 2 commits into
oss-slu:developfrom
sakshar2303:fix/use-deploy-key-for-gh-pages

Conversation

@sakshar2303

@sakshar2303 sakshar2303 commented Apr 11, 2026

Copy link
Copy Markdown
Contributor

Summary

Fixes #461

Root Cause

The deploy step was using GITHUB_TOKEN which does not have admin access
and cannot bypass branch protection rules on the gh-pages branch.

Changes in javadoc-gh-pages.yml

  • Replaced github_token: ${{ secrets.GITHUB_TOKEN }} with
    deploy_key: ${{ secrets.ACTIONS_DEPLOY_KEY }} to allow bypassing
    branch protection rules on gh-pages
  • Removed if: github.ref == 'refs/heads/develop' so deployment also
    runs on main
  • Removed user_name and user_email as they are not needed with a
    deploy key

@sakshar2303

Copy link
Copy Markdown
Contributor Author

please review and merge .

Signed-off-by: Leandru Martin <122942864+leandrumartin@users.noreply.github.com>
@leandrumartin
leandrumartin merged commit b9bdde0 into oss-slu:develop May 25, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update Javadoc publishing and deployment

2 participants