Skip to content

Conversation

@freddyaboulton
Copy link
Contributor

Pull Request Description

Fixes #2898


After creating the pull request: in order to pass the release_notes_updated check you will need to update the "Future Release" section of docs/source/release_notes.rst to include this pull request by adding :pr:123.

@codecov
Copy link

codecov bot commented Oct 12, 2021

Codecov Report

Merging #2899 (f5fb19d) into main (3bca25f) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@          Coverage Diff          @@
##            main   #2899   +/-   ##
=====================================
  Coverage   99.7%   99.7%           
=====================================
  Files        302     302           
  Lines      28392   28392           
=====================================
  Hits       28296   28296           
  Misses        96      96           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3bca25f...f5fb19d. Read the comment docs.

Copy link
Collaborator

@jeremyliweishih jeremyliweishih left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

love it! cleared up my understanding as well 👍

Copy link
Contributor

@eccabay eccabay left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Just have one clarifying question, but this is a great overview.

contributing.md Outdated
Comment on lines 133 to 135
make the check green. To add the dependency, clone the [feedstock](https://github.com/conda-forge/evalml-core-feedstock),
check out `latest_release_changes` and add the dependency to `evalml-core` if it is a core dependency or `evalml` if it is an
extra dependency. Push this change up and rerun `build_conda_pkg` on your branch.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To clarify, does this mean that updating the latest_release_changes branch from your local feedstock fork will somehow update the original feedstock repo's latest_release_changes? Or is there another step here that I'm missing?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah great question! No need to fork in this case. Just push changes up to the "original" repo! I will clarify this point!

@freddyaboulton freddyaboulton force-pushed the 2898-update-conda-contributing-guide branch from 5a240d8 to f5fb19d Compare October 12, 2021 19:59
@chukarsten chukarsten merged commit 939ff9f into main Oct 12, 2021
@freddyaboulton freddyaboulton deleted the 2898-update-conda-contributing-guide branch October 12, 2021 22:27
@chukarsten chukarsten mentioned this pull request Oct 14, 2021
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.

Improve the "Updating our conda package" section of our contributing page.

5 participants