You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To push the automation even further, maybe there could be an additional workflow that would create the new changelog entry and do the full release right after?
The changelog entry would be added as a single commit, and the next commit would be the publish commit.
This would slightly change the current workflow of having the changelog entry added as a PR.
Proposed Solution
Probably folks can already do that with the jupyter_releaser CLI already, and that workflow could even live in their repo directly.
So we could either document such workflow, or add it to the releaser repo like the existing ones.
Problem
To push the automation even further, maybe there could be an additional workflow that would create the new changelog entry and do the full release right after?
The changelog entry would be added as a single commit, and the next commit would be the publish commit.
This would slightly change the current workflow of having the changelog entry added as a PR.
Proposed Solution
Probably folks can already do that with the
jupyter_releaser
CLI already, and that workflow could even live in their repo directly.So we could either document such workflow, or add it to the releaser repo like the existing ones.
Additional context
cc @martinRenou who was interested in this
The text was updated successfully, but these errors were encountered: