Practice & Assessment
Test your understanding of Writing Your First Pull Request
Multiple Choice Questions
5Which GitHub keyword in a PR body automatically closes a linked issue when the PR merges?
A reviewer leaves a comment asking you to refactor a function you did not touch. You disagree because it is out of scope. What is the best response?
Your PR has a failing lint check in GitHub Actions. The merge button is grayed out. What is the correct first step?
What is the purpose of opening a Draft PR?
You open a PR and a maintainer closes it saying it is a duplicate of a previous issue closed as wontfix. What should you do?
Coding Challenges
1PR Description Generator CLI Tool
Build a CLI tool in any language that takes a git branch name, a linked issue number, and a short description as inputs, then outputs a fully formatted PR description with What / Why / Testing / Checklist sections. The tool should validate that the branch name follows the type/description pattern and warn if it does not. Input: --branch (string), --issue (integer), --description (string). Output: formatted Markdown PR body printed to stdout, with a WARN line if branch name is non-standard. Estimated time: 20-25 minutes.
Mini Project
Open Source PR Portfolio -- Three Real Submissions
Submit three pull requests to real open source projects. At least one must be a bug fix, at least one must be a documentation improvement, and at least one must address a CI failure or test gap. For each PR: write a description following the What/Why/Testing template, link it to an issue, respond to all reviewer feedback within 48 hours, and document the outcome. Compile all three PRs into a PORTFOLIO.md with: the repo, issue linked, PR URL, reviewer feedback summary, outcome (merged/closed/pending), and what you learned. This project applies PR writing, self-review, CI debugging, and feedback response skills from every lesson in this module.