-
Notifications
You must be signed in to change notification settings - Fork 684
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
Change cleanlab version in Image Tutorial #138
Conversation
Codecov Report
@@ Coverage Diff @@
## master #138 +/- ##
==========================================
- Coverage 87.29% 86.89% -0.40%
==========================================
Files 12 11 -1
Lines 968 908 -60
Branches 175 166 -9
==========================================
- Hits 845 789 -56
+ Misses 104 103 -1
+ Partials 19 16 -3
Continue to review full report at Codecov.
|
need to fix collab version before we merge |
6ee01b6
to
f53f66e
Compare
@@ -48,6 +48,33 @@ jobs: | |||
- name: Install dependencies | |||
run: python3 -m pip install -r docs/requirements.txt | |||
|
|||
- name: Find and replace "%pip install cleanlab" with master branch in .ipynb files | |||
if: ${{ github.ref_type == '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.
will this work for when we merge PRs into master also?
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.
Yes, it should. It may look a little odd because there isn't an if...else
statement here, so it's just 2 separate if
statements - one for when the doc CI is triggered by a push to the master
branch, another when it's triggered by a newly published release.
In pseudocode, the above-highlighted code snippet does the following:
- If it's triggered by a push to a branch, i.e. the
master
branch in thecleanlab/cleanlab
repo AKA our production repo - find
%pip install cleanlab # for colab
in the.ipynb
files and replace them with pip installing a specific commit hash of cleanlab. For example, if the doc build is run in thecleanlab/cleanlab
repo and the merging commit hash isabc123
, then the replacement will be:
%pip install git+https://github.com/
cleanlab
/cleanlab.git@
abc123
if this is unnecessarily specific, setting it to download to a specific branch would work too, e.g. something like:
%pip install git+https://github.com/
cleanlab
/cleanlab.git@
master
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
This PR introduces:
cleanlab
's latest API (AKA the upcoming v2.0.0 API)gh-pages.yaml
) to dynamically install different versions ofcleanlab
in the .ipynb notebooks based on whether it is triggered by a push tomaster
branch or a new release.cleanlab-docs
repo.cannot import name 'escape' from 'jinja2'
issue.