-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
no documentation built or published with new tag #1128
Comments
https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#push
We have name: Publish Sphinx Docs to GitHub Pages
on:
# Triggers the workflow on push events but only for the main branch
push:
branches:
- main So if you push a - name: Publish if refs/tags
# remove/comment next line to push right away
if: startsWith(github.ref, 'refs/tags')
uses: ad-m/github-push-action@master
with:
github_token: ${{ secrets.GITHUB_TOKEN }}
branch: gh-pages |
I guess you pushed the tag to another branch instead of the Try this
Note: no commit or pull request are involved here. You simply push a tag to the main branch. |
Appears to be the case. I will tag again and confirm if docs are built & published. |
No publishing workflow run when new tag pushed. Only syntax checks. |
The workflow file might need this name: Publish Sphinx Docs to GitHub Pages
on:
# Triggers the workflow on push events but only for the main branch
push:
branches:
- main
tags:
- '*' # all tags, but maybe we want to filter for release tags with 'v*' |
I agree. Without such a change, the workflow only runs on pushes to main. A new tag only will not pass this test. |
Apparently, Peter a tag, then I pushed the same one (and somehow did not catch his in the process). Thanks for the fix, @woutdenolf ! |
The docs are deployed: https://nexusformat.github.io/definitions/ But the official webpages links are broken https://www.nexusformat.org/ |
Ah ok, you made #1129 |
Also see #1130 for new problem |
Once the definitions repository was tagged with 2022-06rc0, no new documentation was built or published.
@woutdenolf
How is this supposed to work?
The text was updated successfully, but these errors were encountered: