events.action: opened
events.author: Tomcli
events.text: **Which issue is resolved by this Pull Request:** 
  Resolves #
  
  **Description of your changes:**
  Update the lightweight_component.ipynb to align with the KubeflowDojo. Also extract the pipeline code from notebook into .py files for easier development and demo.
  
  **Environment tested:**
  
  * Python Version (use `python --version`):
  * Tekton Version (use `tkn version`):
  * Kubernetes Version (use `kubectl version`):
  * OS (e.g. from `/etc/os-release`):
  
  **Checklist:**
  - [x] The title for your pull request (PR) should follow our title convention. [Learn more about the pull request title convention used in this repository](https://github.com/kubeflow/pipelines/blob/master/CONTRIBUTING.md#pull-request-title-convention). 
  
     PR titles examples:
      * `fix(frontend): fixes empty page. Fixes #1234`
         Use `fix` to indicate that this PR fixes a bug.
      * `feat(backend): configurable service account. Fixes #1234, fixes #1235`
         Use `feat` to indicate that this PR adds a new feature. 
      * `chore: set up changelog generation tools`
         Use `chore` to indicate that this PR makes some changes that users don't need to know.
      * `test: fix CI failure. Part of #1234`
          Use `part of` to indicate that a PR is working on an issue, but shouldn't close the issue when merged.
  
  - [ ] Do you want this pull request (PR) cherry-picked into the current release branch?
      
      If yes, use one of the following options:
    
      * **(Recommended.)** Ask the PR approver to add the `cherrypick-approved` label to this PR. The release manager adds this PR to the release branch in a batch update.
      *  After this PR is merged, create a cherry-pick PR to add these changes to the release branch. (For more information about creating a cherry-pick PR, see the [Kubeflow Pipelines release guide](https://github.com/kubeflow/pipelines/blob/master/RELEASE.md#option--git-cherry-pick).)
events.title: fix(samples): Add compilable python file for lightweight and e2e-mnist example
events.type: issue
events.action: created
events.author: Tomcli
events.text: /cc @ckadner
events.type: comment
events.action: created
events.author: animeshsingh
events.text: /lgtm
events.type: comment
events.action: created
events.author: animeshsingh
events.text: Is this good to merge @ckadner ?
events.type: comment
data_with_bots.bot: New changes are detected. LGTM label has been removed.
data_with_bots.meta: This message directly preceded comment from bot *k8s-ci-robot* by author *animeshsingh*:
data_with_bots.text: Is this good to merge @ckadner ?
data_without_bots.meta: This message directly preceded comment from bot *k8s-ci-robot* by author *animeshsingh*:
data_without_bots.text: Is this good to merge @ckadner ?