Build and Share a Real GitHub Repository

The capstone project for Git & GitHub for Beginners — a free Data & Tech course. Pass it and you earn a certificate anyone can verify.

Start the course free Download the project workbook

The project unlocks once you complete the lessons. The workbook is free to download now so you can see exactly what is expected.

What you will submit

The public URL of your finished GitHub repository, which must show a commit history on main, a merged pull request from a feature branch, a README, and a .gitignore.

What to do, step by step

  1. Create a new public repository on GitHub (using the email that matches your Git config so your commits count) and connect it to a local Git repo with git remote add origin, git branch -M main, and git push -u origin main.
  2. Make at least three separate commits directly on main, each with a clear, present-tense message (e.g. 'Add project structure', 'Add naira-to-dollar converter logic') — no lazy messages like 'update' or 'stuff'.
  3. Create a feature branch with git checkout -b feature-something, add at least two more commits on it, and push the branch to GitHub.
  4. Open a pull request from your feature branch into main with a clear title and a description of what you changed and why, then merge it and delete the branch.
  5. Add a strong README.md (in Markdown) containing the project name, a one-line description, a Features list, a 'How to run it' section, the technologies used, and your name/contact.
  6. Add a .gitignore that excludes secrets and junk (at minimum .env and any node_modules/ or log files) so no sensitive data is ever committed.

Files to work with

Project workbook (fill in, then submit)The whole brief, an evidence checklist, the grading rubric as a self-check and the link-sharing steps in one file. Opens in Word, Google Docs or WPS.Word · 6 KB

How it is graded

CriterionWeight
Repo is public and reachable, with at least three meaningful commits on main using clear, present-tense messages25%
A feature branch was created, committed to, and merged into main via a properly described pull request30%
README.md is present, written in clean Markdown, and covers description, features, how-to-run, technologies and contact25%
A .gitignore is present and correctly excludes secrets/junk (e.g. .env), showing security awareness10%
Overall repository is tidy and professional — sensible name, no leaked secrets, coherent history a recruiter could read10%

You need 65% overall to pass. A failed submission comes back with feedback and can be revised and resubmitted.

Before you submit: make your link public

If your work lives in Google Drive or Google Docs, open Share → General access and change “Restricted” to “Anyone with the link” (Viewer). Then paste the link into a private browser window: if it opens without sign-in, you are ready. A private link cannot be graded — it is the single most common reason a good project fails.

Frequently asked questions

Do I have to finish Git & GitHub for Beginners before submitting the project?

Yes. The submission screen opens once every lesson in Git & GitHub for Beginners is marked complete. The lessons are where the methods, the Nigerian context and the worked examples the project depends on are taught.

How is the project graded?

An examiner scores each rubric criterion from 0 to 100 and weights them as shown on this page; you need 65% overall to pass. Most submissions are graded within minutes and you get written feedback on what was strong and what to improve.

Can I resubmit if I fail?

Yes. A failed project comes back with feedback; revise the weak parts and resubmit. A passed project is final — the certificate is issued and cannot be re-rolled.

What do I actually submit?

A write-up of what you did (under 5,000 characters) plus a public link to your work — a Google Drive folder, Google Doc, spreadsheet, GitHub repository or video. The link must open without sign-in; a private link cannot be graded. The free project workbook on this page walks you through all 6 steps.

Is the certificate real?

Yes. Passing this project issues a certificate with a unique verification code. Anyone — an employer, a client, a school — can open the verification page and see that the certificate is genuine and which project earned it.

More Data & Tech projects

Ready to earn this certificate?

Git & GitHub for Beginners is free and self-paced. Finish the lessons, complete this project, and the certificate is yours to share.

Start learning free