-
Notifications
You must be signed in to change notification settings - Fork 92
Update conda section of contributing guide #2899
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
Conversation
Codecov Report
@@ 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.
|
39027b0 to
5a240d8
Compare
jeremyliweishih
left a comment
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.
love it! cleared up my understanding as well 👍
eccabay
left a comment
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.
LGTM! Just have one clarifying question, but this is a great overview.
contributing.md
Outdated
| 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. |
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.
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?
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.
Ah great question! No need to fork in this case. Just push changes up to the "original" repo! I will clarify this point!
5a240d8 to
f5fb19d
Compare
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.rstto include this pull request by adding :pr:123.