Skip to content
BasicsOpenAlt AI Labs

Your first GitHub repo, with three commits

A free starter challenge. Create a GitHub account, make your first public repository with a real README, and save your work in three clear commits.

  1. 1Learn
  2. 2Do
  3. 3Submit
  4. 4Results
Category
Basics
Lesson
20 min
Effort
~2h
Prize
Free
Closes in
 

Learn

20 min lesson

What you'll learn

How to create a GitHub account, make your first repository, write a README and save your work in three commits. GitHub is where developers keep and share code, and it is the first place an employer looks.

Create the account

Sign up at github.com with the professional email you use for school or work. Pick a username close to your real name, such as aigerimt or a-toktosunova; you will put it on your CV. Turn on two-factor authentication in Settings, under Password and authentication. GitHub requires it for anyone who contributes code, so do it now. You must be at least 13.

Your first repository

A repository, or repo, is a folder with a memory: it remembers every version of every file. Click New repository. Give it a short name in lowercase with dashes, such as my-first-repo or bishkek-food-notes. Make it public. Tick "Add a README file".

Write a real README

The README is the front page of your repo. Open it, click the pencil, and write in Markdown:

  • A title with #
  • Two sentences about who you are and why this repo exists
  • A short list of three things you want to learn this year
  • A link to one thing you like on the internet

Keep it honest and simple. Markdown is just text with a few symbols: # for headings, - for lists, **bold** for bold.

Three commits

A commit is a saved step with a message that says what changed. Make three, each with a different change and a clear message:

  1. Write the README (the first commit already happens when you create the repo; edit it and commit with a message like "Write the introduction").
  2. Add a new file, for example notes.md with what you learned today. Message: "Add learning notes".
  3. Change something: fix a typo, add a section. Message: "Add list of goals".

Good messages start with a verb and say what the commit does. "update" or "asdf" tells nobody anything.

You can do all of this in the browser. If you want to try the real developer way, install Git or GitHub Desktop, clone the repo, edit on your computer and push. Both count.

Before you submit

Open your repo while signed out, or in a private window. You should see the README rendered on the front page and "3 commits" or more in the history. Copy the URL, such as https://github.com/aigerimt/my-first-repo, and submit it.

Finish the lesson to unlock submitting.

Sign in to start learning

Do

about 2h of work

The task

GitHub is where code lives, and your GitHub profile is the first thing an engineering team opens when they look at you. Every coding challenge on Alt AI Labs is handed in through it. In this challenge you create an account with a professional username, turn on two-factor authentication, make a public repository, write a README in Markdown that introduces you, and make three commits with clear messages. You can do it all in the browser or with Git on your computer.

Deliverables

  1. 01The URL of your public repository
  2. 02A README that introduces you and the repo
  3. 03At least three commits with clear messages

Acceptance criteria

Judged against exactly these

  • The repository is public and opens for someone who is signed out
  • The README renders on the repo front page with a heading, at least two sentences and a list
  • The history has at least three commits made during the challenge window, each changing something different
  • Every commit message says what changed, such as "Add learning notes", not "update" or "asdf"
  • The username is close to your real name

Rules

  • Complete the lesson first. The submit form unlocks once you mark it done.
  • Submit a link to your work: a public GitHub repo or PR for code challenges; YouTube, Google Drive or Docs, Figma, Notion or a live site for everything else.
  • AI tools are allowed and encouraged. Plagiarised or copied work is disqualified.
  • The work must be made during the challenge window. For code, the commit history must show it.
  • An AI reviewer pre-scores every entry against the acceptance criteria. A human makes the final decision.
  • On payout, Alt AI Labs receives a licence to use the winning work (MIT for code). Non-winning entries stay yours.
  • Do not include secrets, API keys or anyone's personal data.
  • GitHub requires you to be at least 13.
gitgithubmarkdown

Submit

Sign in and complete the lesson to submit. Entry is free.

Sign in

Results

  1. 01

    AI pre-score

    AI reviews your write-up against the acceptance criteria. It cannot open your link, so explain your work clearly.

  2. 02

    Human decision

    A human reviews the work itself and makes the final call. The AI score is advisory.

  3. 03

    Win

    There is no cash prize. Winning work is shown to the organization behind the challenge.

Posted by

Alt AI Labs