Skip to content
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

Merged
merged 5 commits into from
Nov 8, 2022
Merged

Add create feedstock PR workflow #346

merged 5 commits into from
Nov 8, 2022

Conversation

gsheni
Copy link
Contributor

@gsheni gsheni commented Nov 3, 2022

No description provided.

@gsheni gsheni self-assigned this Nov 3, 2022
@codecov
Copy link

codecov bot commented Nov 3, 2022

Codecov Report

Merging #346 (d2e0e27) into main (2a6a8b2) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #346   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           29        29           
  Lines         1333      1333           
=========================================
  Hits          1333      1333           

@gsheni gsheni marked this pull request as ready for review November 3, 2022 17:53
* Enhancements
* Add create feedstock PR workflow (:pr:`346`)
Copy link
Contributor

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"
Copy link
Contributor

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?

@gsheni gsheni merged commit 30238fe into main Nov 8, 2022
@gsheni gsheni deleted the add_conda_create branch November 8, 2022 18:32
@gsheni gsheni mentioned this pull request Jan 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants