FAQ: Deploy Your Website to GitHub Pages - Create Your Repo


This community-built FAQ covers the “Create Your Repo” exercise from the lesson “Deploy Your Website to GitHub Pages”.

Paths and Courses
This exercise can be found in the following Codecademy content:

Deploy a Website

FAQs on the exercise Create Your Repo

There are currently no frequently asked questions associated with this exercise – that’s where you come in! You can contribute to this section by offering your own questions, answers, or clarifications on this exercise. Ask or answer a question by clicking reply (reply) below.

If you’ve had an “aha” moment about the concepts, formatting, syntax, or anything else with this exercise, consider sharing those insights! Teaching others and answering their questions is one of the best ways to learn and stay sharp.

Join the Discussion. Help a fellow learner on their journey.

Ask or answer a question about this exercise by clicking reply (reply) below!

Agree with a comment or answer? Like (like) to up-vote the contribution!

Need broader help or resources? Head here.

Looking for motivation to keep learning? Join our wider discussions.

Learn more about how to use this guide.

Found a bug? Report it!

Have a question about your account or billing? Reach out to our customer support team!

None of the above? Find out where to ask other questions here!


" our repo’s name must also follow GitHub Pages’ naming convention, otherwise your site will not publish at all."

I dont understand this part. Why we have to place the repo name like “your-user-name.github.io”. What if I host 2 repositories?


I came across these error message. What should I do?

Admin@User-PC MINGW64 ~/Desktop/html/halimjon.com/my-portfolio-site (master)
$ git push -u origin master
To https://github.com/HalimHamidov/halim.github.io.git
 ! [rejected]        master -> master (fetch first)
error: failed to push some refs to 'https://github.com/HalimHamidov/halim.github.io.git'
hint: Updates were rejected because the remote contains work that you do
hint: not have locally. This is usually caused by another repository pushing
hint: to the same ref. You may want to first integrate the remote changes
hint: (e.g., 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.