Add create feedstock PR workflow#2181
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2181 +/- ##
=======================================
Coverage 99.29% 99.29%
=======================================
Files 145 145
Lines 17556 17556
=======================================
Hits 17432 17432
Misses 124 124 Continue to review full report at Codecov.
|
thehomebrewnerd
left a comment
There was a problem hiding this comment.
Is the intent for this to create a PR or just get everything ready and then we have to manually launch the PR with the last link that is echoed?
Also, should we create a branch in the forked repo rather than pushing the updated meta.yaml to main?
| @@ -0,0 +1,55 @@ | |||
| on: | |||
| workflow_dispatch: | |||
There was a problem hiding this comment.
Is the idea here that once the pypi release is done we would manually trigger this workflow with the new version to create the feedstock PR?
There was a problem hiding this comment.
I have updated release.md with the instructions
There was a problem hiding this comment.
Could the release github action kick off this workflow after it finishes the pypi upload?
Co-authored-by: Roy Wedge <roy.wedge@alteryx.com>
|
|
||
| ## Release on conda-forge | ||
|
|
||
| In order to release on conda-forge, you can either wait for a bot to create a PR, or manually kickoff the creation with GitHub Actions |
There was a problem hiding this comment.
After we've confirmed the release workflow can kick off the action we should update this section
Co-authored-by: Roy Wedge <roy.wedge@alteryx.com>
392d30b to
bbf6e81
Compare
Uh oh!
There was an error while loading. Please reload this page.