Build & submit taskBetaintermediate

Make a Repository Team-Ready

Prepare a small website's repository for a team: code owners, a pull request template, a commit-msg hook enforcing Conventional Commits, signed commits, and a signed release tag with the right Semantic Version. A local self-check verifies every piece, including the signatures, 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.

CODEOWNERS uses the last matching line, so general rules come first.

Conventional Commits make history machine-readable: feat means a minor version, fix a patch, a ! or BREAKING CHANGE a major one.

An SSH signature ties a commit or tag to a key, and Git verifies it against an allowed signers file.

The scenario

Bean There's website has been a one-person repository, released as v1.0.0. Next week it gets a team: Alex looks after the prices, Priya the docs, and two new people start.

Before they arrive, you set the repository up so work arrives in a predictable shape: the right reviewers, a description for every pull request, readable commit messages, verifiable authorship, and a signed release.

Your role

You are the developer making the repository team-ready. Your deliverable is cafe-site with a CODEOWNERS file and a pull request template, a working commit-msg hook, new commits that follow Conventional Commits and are all signed, a feat: commit adding scones.md, a signed v1.1.0 tag on the newest commit, and notes on rules, branching strategy and leaked secrets.

Start the task to unlock the full brief

You'll get the step-by-step requirements, setup commands, the 4-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: About code owners

docs.github.com

Conventional Commits 1.0.0

conventionalcommits.org

GitHub Docs: Telling Git about your signing key

docs.github.com

git hook documentation

git-scm.com

Set up a Git repository for a team, hands-on

A repository a team can rely on needs more than code: owners who review the right files, a pull request template, commit messages a release tool can read, signatures that prove who made each commit, and a signed release. This kit gives you a small website's repository at v1.0.0 and a ready-made commit-msg hook. You add CODEOWNERS and a template, enforce Conventional Commits, sign your commits with your SSH key and cut a signed v1.1.0. A local self-check verifies every piece, signatures included, and writes your submission only when everything genuinely passes. It is the Level 7 project in Preporato's Git course.

Frequently asked questions

Do I need GitHub for this project?

No. Everything is checked on your computer, including the signatures, using an allowed signers file. The CODEOWNERS file and the pull request template are the same files GitHub reads when you push the repository later.

My Git is older than 2.54. Can I still do it?

Yes. Config-based hooks need Git 2.54, but you can copy the hook to .git/hooks/commit-msg instead. SSH signing needs Git 2.34 or newer.

Why does check.sh say my commits have no good signature?

Usually because Git can't verify them yet: set gpg.ssh.allowedSignersFile to a file listing your commit email and public key. A commit made before you turned signing on can be re-signed with git commit --amend --no-edit if it's the newest one.