-
Notifications
You must be signed in to change notification settings - Fork 47
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
Add create feedstock PR workflow #346
Conversation
Codecov Report
@@ Coverage Diff @@
## main #346 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 29 29
Lines 1333 1333
=========================================
Hits 1333 1333 |
docs/source/release_notes.rst
Outdated
* Enhancements | ||
* Add create feedstock PR workflow (:pr:`346`) |
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.
Minor nitpick, but should this be somewhere else, like Testing Changes
since this isn't an enhancement a Compose user would see? I have tended to think of Enhancements as user-facing improvements, but not sure that is the right way to look at it.
with: | ||
project: "compose" | ||
pypi_version: ${{ github.event.inputs.version }} | ||
project_metadata_filepath: "composeml/pyproject.toml" |
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.
Should this be compose
or composeml
here? Not exactly clear to me which we should use, but thought maybe since we used compose
on L18, it should also be compose
here?
No description provided.