Season 3: Welcome to Engineering · Episode 5 of 8
Your First Pull Request
You play: AI Engineering Intern
Included with Core programme and Certification prep
The situation
A creator reported that the monthly export crashes when their batch is empty. Leo is separately building a monthly summary view on a branch. Both changes touch the same file, and Lydia wants the whole thing traceable: an issue, a branch, a reviewed pull request, and a clean merge.
What you'll learn
- GH-900 collaboration and projects: issues, pull requests, discussions, reviews, labels, milestones, project views, and resolving merge conflicts.
- Choosing between Issues, Discussions, Projects, wikis, Pages and Gists; closing keywords, issue templates, assignees and notification settings; Projects table, board and roadmap layouts, workflows, insights, milestones and saved replies.
Who you work with
Maya Chen
Senior AI Engineer · Your mentor
Lydia Roe
Security Engineer
Leo Martins
Product Manager
Scenes
- 1.Where does this conversation go?
- 2.The right surface for each thing
- 3.Which GitHub feature?
- 4.Issue to branch to pull request
- 5.Two changes, one file
- 6.Collaboration check
What you leave with
The export crash went from a chat message to a closed issue with a traceable line through it: issue #14, a branch, a reviewed pull request, a merge. And when Leo's summary branch conflicted, you resolved it to keep both changes rather than picking a side.