Build & submit taskBetabeginner

Ship a Change Through a Pull Request

Put a small website on GitHub, deal with a teammate's edit you didn't have without losing it, and ship a change through a pull request: a clear description, a suggested change from review, a merge commit and a tidy laptop afterwards. A local self-check reads your repository and GitHub through git and writes your submission for instant, rubric-based feedback.

45 min

Est. time

Outcomes

Rubric criteria

60%

Pass score

What you'll learn

Skills you'll have real reps in after shipping this.

A refused push means the server has work you don't. Pulling first keeps everyone's commits; --force would throw a teammate's away.

A pull request is a branch plus a conversation: a description that says why, review comments, suggested changes and a merge button.

Merging on GitHub doesn't touch your laptop: pull, delete the local branch and prune to stay in step.

The scenario

Bean There, a small coffee shop, wants its website on GitHub so the team can work on it together. The site is a repository on your laptop with three commits and no remote.

You put it on GitHub, then play both parts of a small team: a teammate edits the README in the browser while you commit on your laptop, and later you ship the shop's new Sunday hours through a pull request, reviewed with a suggested change, merged and cleaned up.

Your role

You are the developer who sets up the team's repository and ships the first change through review. Your deliverable is a GitHub repository whose main holds the teammate's web edit and your own commit together, a pull request merged with a merge commit that includes an applied suggestion, no leftover branches on GitHub or your laptop, and short notes with the pull request's link and description.

Start the task to unlock the full brief

You'll get the step-by-step requirements, setup commands, the 5-criterion grading rubric, tips, and the ability to submit your solution for instant AI grading.

Free to start · submit when you're ready

Learning resources

GitHub Docs: Creating a pull request

docs.github.com

GitHub Docs: Incorporating feedback in your pull request

docs.github.com

GitHub Docs: About pull request merges

docs.github.com

git push documentation (note about fast-forwards)

git-scm.com

Practise pull requests on GitHub, end to end

Pull requests are how most teams get work into main, and the first one is easier with a guided project. This kit gives you a small website to put on GitHub. You handle a teammate's edit you didn't have (the classic refused push), then ship a change through a pull request with a proper description, apply a reviewer's suggested change, merge it with a merge commit and tidy up your laptop afterwards. A local self-check verifies everything through git, including GitHub's pull request refs, and writes your submission only when it genuinely passes. It is the Level 3 project in Preporato's Git course.

Frequently asked questions

Do I need a GitHub account?

Yes, a free one. The project happens on GitHub itself: you create a repository, edit in the browser, open and merge a pull request. Your terminal needs to be signed in to GitHub, which Level 3 of the course walks through.

Can I review my own pull request?

You can comment and suggest changes on your own pull request, and apply your own suggestion, which is what this project asks. GitHub doesn't let authors approve their own pull requests, so no approval is needed.

What if I merge with Squash and merge by mistake?

Make another small change on a new branch, open a second pull request and merge that one with Create a merge commit. check.sh looks for at least one pull request merged with a merge commit.