-
Notifications
You must be signed in to change notification settings - Fork 5
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
ci: Delete/remove release tag after CHANGELOG.rst modified in main
, build docs as a part of the release workflow after github release
#120
Conversation
@@ -35,7 +35,7 @@ jobs: | |||
- name: Check out ${{ inputs.project }} | |||
uses: actions/checkout@v4 | |||
with: | |||
fetch-depth: 0 # Fetches branches and tags | |||
ref: main # Fetch the main branch with CHANGELOG.rst modified during full release |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Problem 2 - release notes never displayed the latest version
I found the source of the problem why changelog didn't show the latest version upon release.
When push a tag (commit) to upstream
, the tag does not contain updated CHANGELOG.rst. The CHANGELOG.rst is modified during the CI which has an additional commit in main
.
Hence, when we build a doc, we should checkout main
instead of the tag
!
@sbillinge ready for review |
please see my comments on the diffpy.utils PR. I wonder if this is the right approach actually. |
@@ -97,13 +129,13 @@ jobs: | |||
token: ${{ secrets.GITHUB_TOKEN }} | |||
|
|||
github-release: | |||
needs: [update-changelog] | |||
needs: [delete-create-new-tag] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
must have delete-create-new-tag
which depends on build-changelog
@sbillinge ready for review - tested using a dummy repo/org. https://bobleesj-test-org.github.io/bobleesj.release/release.html |
main
, build docs as a part of the release workflow after github release
looks good, let's try it..... I will merge. Does diffpy.utils have to be updated, or this will just run if I merge it into v0? |
No updates needed.. on diffpy.utils. |
Closes #94
I think it is better to read this PR diffpy/diffpy.utils#312 first since it's related and I provide a bit more context on the problem.
Please see in-line comments: