Replies: 2 comments 2 replies
-
Yea makes more sense to have it's own workflow I think. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Not totally sure yet what @kaitj has planned with the release drafter, but I think part of the idea is to deploy when a new release is published on Github? So would we make a new workflow that runs in response to release publication? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Just a small point of confusion for me. Currently, linting, testing and deploying are all in a single workflow that runs on every merge and pull request. Admittedly, deploy only runs when a tag is pushed, but doesn't that mean that if a PR with a tag is pushed, it will immediately publish the PR?
Perhaps deployment should be moved to its own workflow?
Beta Was this translation helpful? Give feedback.
All reactions