Catch up main with changes from v0.2.1 (#806)

* bump up the version

* copying over the items from platform-demo

* minor edits to the self-hosting-demo

* Update README.md

* Update README.md

* update demo notebook tagging

* Add tutorials to docs

* first attempt at the github action. flood gates will open after MJL finishes his copy

* also copy our favourite tutorial for the same treatment as other demos.

* Add artifact store file for main PR (#798)

* Update and reorganize RTD docs (#795)

* Move intro text to pipeline's TOC section

* Reorganize RTD pages related to artifact storage

* Add a new section on using existing artifacts

* Update index.rst

minor change

* Update index.rst

minor tweaks

* Update s3.rst

minor tweak

* Update s3.rst

@yoonspark let me know if this modification makes sense

* Fix typos; remove duplacate doc

* For Postgres and S3, make clearer distinction between storing artifact values vs. metadata

* Add phrasing suggested by MMA

Co-authored-by: Moustafa AbdelBaky <[email protected]>

* Add mkdir step before cp (#799)

* Lin 621 migrate everything from demos repo to lineapy examples (#794)

* Copy demos repo stories
* Exclude self-hosting-lineapy notebooks from CI
* Use zip artifact store file
* Skip cell due to bugs in pandas
Only happen in python 3.10, so not going to force updating pandas version in requirements.
Related pandas-dev/pandas#41935

Co-authored-by: Humble bot servant <[email protected]>

* Add tutorials to docs

* Lin 621 cleanup nbval prefix (#800)

* Fix mkdir demos error and remove NBVAL_prefix in demos notebooks
* Exclude notebooks in demos from CI

* Modify a comment to trigger demo copy (#803)

* Modify a comment
* Add tutorials to docs

Co-authored-by: Humble bot servant <[email protected]>

* get rid of is_demo. es confuso

* add lineapy install at the top.

* Add tutorials to docs

* load lineapy as an extension.

* Add tutorials to docs

* refresh all the tags and rebuild demos.

* Add tutorials to docs

* two actions were competing with each other. arranging for both demos and docs folder to sync together and commit only once (might need to merge into main for this to work)

* add explicit image for colab

* Refresh demos folder and update docs

* start using lineapy/main images for colab

* Refresh demos folder and update docs

* remove references to demos repo from readme.

* remnove the referrences to binder. update bitly link for api basics.

* Refresh demos folder and update docs

* update links pointing to demos repo back to lineapy.

* delete unused files inside docs

* move demos folder to be .colab

* Update the bitly links

* bump up version to 0.2.1

* demos was renamed.

Co-authored-by: Moustafa <[email protected]>
Co-authored-by: dorx <[email protected]>
Co-authored-by: Humble bot servant <[email protected]>
Co-authored-by: Mingjer Lee <[email protected]>
Co-authored-by: Sangyoon Park <[email protected]>

Author: 6 people

.colab/00_api_basics.ipynb

@@ -15,15 +15,15 @@ jobs:
         with:
           fetch-depth: 0 # otherwise, there would be errors pushing refs to the destination repository.
 
-      - name: "Copy demo notebooks to top level demos folder"
-        run: mkdir -p demos/ && cp -R examples/use_cases/* demos/ && cp examples/tutorials/00_api_basics.ipynb demos/
+      - name: "Copy demo notebooks to top level .colab folder"
+        run: mkdir -p .colab/ && cp -R examples/use_cases/* .colab/ && cp examples/tutorials/00_api_basics.ipynb .colab/
 
       - name: "copy example notebooks to docs"
         run: cp examples/tutorials/00_api_basics.ipynb docs/source/tutorials/
 
       - name: "Regex out the NBVAL_SKIP and NBVAL_IGNORE_OUTPUT comments"
         run: |
-          cd demos/ 
+          cd .colab/ 
           find ./ -type f -name "*.ipynb" -exec sed -i 's/\#[\ ]*NBVAL_SKIP//g' {} \;
           find ./ -type f -name "*.ipynb" -exec sed -i 's/\#[\ ]*NBVAL_IGNORE_OUTPUT//g' {} \;
 

demos/README.md renamed to .colab/README.md

@@ -20,12 +20,9 @@
 <div align="center" style="display:flex;flex-direction:column;">
     <h3>👇 Try It Out! 👇</h3>
     <div>
-        <a href="https://bit.ly/3N9WvDB">
+        <a href="https://bit.ly/3y5IiSq">
             <img src="https://colab.research.google.com/assets/colab-badge.svg" alt="Open in Colab"/>
         </a>
-        <a href="https://bit.ly/3MyW8RW">
-            <img src="https://mybinder.org/badge_logo.svg" alt="Open in Binder"/>
-        </a>
     </div>
 </div>
 
@@ -67,7 +64,7 @@ One way to deal with this problem is to keep the notebook in sequential operatio
 the entire notebook during development. However, we soon realize that this interrupts our natural workflows and stream of
 thoughts, decreasing our productivity. Therefore, it is much more common to clean up the notebook after development. This is a very time-consuming process and is not immune from reproducibility issues caused by deleting cells and out-of-order cell executions.
 
-To see how LineaPy can help here, check out [this](https://github.com/LineaLabs/demos/blob/main/story/clean_up_a_messy_notebook/clean_up_a_messy_notebook.ipynb) demo or <a href="https://bit.ly/3NMffcb"><img src="https://colab.research.google.com/assets/colab-badge.svg" alt="Open in Colab"/></a>, <a href="https://bit.ly/3O5iJ9H"><img src="https://mybinder.org/badge_logo.svg" alt="Open in Binder"/></a>.
+To see how LineaPy can help here, check out [this](https://github.com/LineaLabs/lineapy/blob/v0.2.x/.colab/clean_up_a_messy_notebook/clean_up_a_messy_notebook.ipynb) demo or <a href="https://bit.ly/3SuC4nm"><img src="https://colab.research.google.com/assets/colab-badge.svg" alt="Open in Colab"/></a>.
 
 ### Use Case 2: Revisiting Previous Work
 
@@ -83,7 +80,7 @@ Or, the person may no longer be in the organization with no proper handover of t
 In any of these cases, it becomes extremely difficult to identify the root of the issue, which may render the result
 unreliable and even unusable.
 
-To see how LineaPy can help here, check out [this](https://github.com/LineaLabs/demos/blob/main/story/discover_and_trace_past_work/discover_and_trace_past_work.ipynb) demo or <a href="https://bit.ly/3GEYM7c"><img src="https://colab.research.google.com/assets/colab-badge.svg" alt="Open in Colab"/></a>, <a href="https://bit.ly/3H9DG14"><img src="https://mybinder.org/badge_logo.svg" alt="Open in Binder"/></a>.
+To see how LineaPy can help here, check out [this](https://github.com/LineaLabs/lineapy/blob/v0.2.x/.colab/discover_and_trace_past_work/discover_and_trace_past_work.ipynb) demo or <a href="https://bit.ly/3fsA9RL"><img src="https://colab.research.google.com/assets/colab-badge.svg" alt="Open in Colab"/></a>.
 
 ### Use Case 3: Building Pipelines
 
@@ -96,7 +93,7 @@ orchestration systems or job schedulers (e.g., cron, Apache Airflow, Prefect). O
 what they are and how to work with them. If not, we need to spend time learning about them in the first place.
 All this operational work involves time-consuming, manual labor, which means less time for us to spend on our core duties as a data scientist.
 
-To see how LineaPy can help here, check out [this](https://github.com/LineaLabs/demos/blob/main/story/create_a_simple_pipeline/create_a_simple_pipeline.ipynb) demo or <a href="https://bit.ly/3x4YOkq"><img src="https://colab.research.google.com/assets/colab-badge.svg" alt="Open in Colab"/></a>, <a href="https://bit.ly/3mCG47e"><img src="https://mybinder.org/badge_logo.svg" alt="Open in Binder"/></a>.
+To see how LineaPy can help here, check out [this](https://github.com/LineaLabs/lineapy/blob/v0.2.x/.colab/create_a_simple_pipeline/create_a_simple_pipeline.ipynb) demo or <a href="https://bit.ly/3SJewuO"><img src="https://colab.research.google.com/assets/colab-badge.svg" alt="Open in Colab"/></a>.
 
 ## Getting Started