Skip to content

Add Week 1 lab1 notebook (Piyush Choudhary) - #1758

Draft
choudharyNik wants to merge 2 commits into
ed-donner:mainfrom
choudharyNik:piyush-choudhary-lab-exercises
Draft

choudharyNik wants to merge 2 commits into
ed-donner:mainfrom
choudharyNik:piyush-choudhary-lab-exercises

Conversation

@choudharyNik

Copy link
Copy Markdown

Summary

  • Adds my Week 1 Lab 1 community contribution notebook under 1_foundations/community_contributions/Piyush_Choudhary_Lab_Exercises/week_1/lab1.ipynb.
  • Uses the Gemini OpenAI-compatible client for the Lab 1 exercise flow.

Test plan

  • Open the notebook in Jupyter/Cursor with the course .venv kernel
  • Run cells top to bottom with GOOGLE_API_KEY and GEMINI_BASE_URL set
  • Confirm the Gemini chat completion call returns a response

@ed-donner
ed-donner marked this pull request as draft November 12, 2026 03:31
@ed-donner

Copy link
Copy Markdown
Owner

Hi @choudharyNik,

I'm super grateful that you've worked on this and are sharing your contribution. It looks like this might not be ready to be merged, so please can I ask you to review this:

https://edwarddonner.com/pr

In this PR, the course's own 1_foundations/twin/linkedin.pdf and summary.txt are replaced with yours, and both notebooks have outputs. Please put those two files back as they are on main, clear the outputs, and push to this branch.

The most common issue is that you've included a file outside community-contributions. This would impact all students on the course. You can see this by going to the "Files changed" tab in this PR; the only changes should be to files in community-contributions.

If there's a good reason to change files outside community-contributions, like an important bug fix, then please let me know (and thank you!)

The 2nd most common reason is that you've not cleared outputs of Notebooks, leading to large code changes. Instructions at the link above.

The 3rd common reason is that you've included too many changes, such as many thousands of lines of code, or a large number of files. I'm grateful for your work, but see the link above for ways we can include this without the repo getting too large.

The PR details in this Github screen shows you the files changed, and at the top right the number of lines added (in Green) and deleted (in Red) by this PR. Typically the Green number should be less than 2,000 and the red number should be 0.

I've set this PR to draft for now, so I can see at a glance which PRs are ready for me. When you've made the change, click "Ready for review" near the bottom of this page and I'll take a look. I very much look forward to merging it!

Thanks so much
Ed

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.

3 participants