Skip to content

fix: deploy GitHub Pages from master branch#130

Closed
sujen1412 wants to merge 4 commits into
developfrom
claude/priceless-napier-b2c198
Closed

fix: deploy GitHub Pages from master branch#130
sujen1412 wants to merge 4 commits into
developfrom
claude/priceless-napier-b2c198

Conversation

@sujen1412
Copy link
Copy Markdown
Contributor

Summary

  • Added master to the push and pull_request branch triggers — the workflow was only watching main and develop, so pushes to master never triggered it
  • Fixed the deploy condition to also match refs/heads/master — the deploy job was gated on refs/heads/main exclusively, so no deployment ever ran

Root cause

The repo's default branch is master, but the workflow was written for main. GitHub Pages showed status: null (never deployed) as a result.

Test plan

sujen1412 and others added 4 commits January 7, 2026 11:35
Add Comprehensive Sphinx-Compatible Documentation
docs: add PyPI installation instructions
The deploy job only triggered on refs/heads/main, but the repo's
default branch is master. Added master to push/PR triggers and
the deploy condition so Pages actually deploys.
@sujen1412 sujen1412 changed the base branch from master to develop May 20, 2026 17:01
@sujen1412
Copy link
Copy Markdown
Contributor Author

Closing this to rebase from develop.

@sujen1412 sujen1412 closed this May 20, 2026
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.

2 participants