Using the command line

1. In your command line, navigate to your project directory. Type git init to initialize the directory as a Git repository.
2. Type git remote add origin https://github.com/AdityaGarg00/github-upload.git
3. Type git add .
4. Type git commit -m "initializing repository"
5. Type git push -u origin main to push the files you have locally to the remote on GitHub. (You may be asked to log in.)

Note: You can also use a password protected SSH key to connect to GitHub. See Connecting to GitHub with SSH in our documentation to learn more.

Using GitHub Desktop

GitHub Desktop doesn't allow you to add a new remote for an existing directory, so instead we'll copy the contents of your existing folder to our repo. If you'd like to keep your existing folder, you may want to use the command line or one of the other tools.

1. In GitHub Desktop, click on File and Clone a repository.
2. Click on the URL tab.
3. Paste the URL from this repository.
4. Move the contents of your local repository to this directory.
5. Create a commit by entering a commit message and then clicking on Commit to main
6. Click Publish branch in the top right corner to push your repository to GitHub.

Using Visual Studio Code

1. In Visual Studio Code, open the folder for your project.
2. Click the icon on the left for Source Control.
3. On the top of the Source Control panel, click the Git icon.
4. If the files you see match the repository you want to create, click Initialize Repository.
5. Next to the word CHANGES, click the symbol of the plus sign to stage all of the changes.
   • This is part of the two stage commit. You can use this staging function to create meaningful commits throughout the development process.
6. In the box in the Source Control panel, type a commit message. Something like "initial commit - moving project" could work.
7. Click the checkmark at the top of the Source Control panel.
8. Open the integrated terminal found under View > Integrated Terminal.
9. In your command line, type git remote add origin https://github.com/AdityaGarg00/github-upload
10. In the Source Control Panel, click the expandable three dots that open a menu of options.
11. When asked if you'd like to publish the branch, click Okay.

Using Atom

1. In Atom, open the folder for your project
2. At the top of your screen, click Packages. Select GitHub, and then toggle the Git Tab from the drop-down menu.
3. Select Create Repository within the Git tab on the right-hand size of your screen.
4. Select Init to accept the default prompt of the pop up window
5. In the Git tab, you can see that your files are ready for staging. It should be accounted for, but double check to make sure that none of your binaries or files that you listed in the .gitignore are listed in this dialog menu.
   - If they are, double check your .gitignore file to make sure they're included or remove them from your directory.
6. Select Stage All
   - This is part of the two stage commit. You can use this staging function to create meaningful commits throughout the development process.
7. In the box at the bottom of the Git panel, type a commit message. Something like "initial commit - moving project" could work.
8. Select Commit
9. Close Atom
10. In your command line, navigate to your project directory.
11. Type git remote add origin https://github.com/AdityaGarg00/github-upload
12. Return to Atom, and select the Up/Down arrow icon at the bottom of your Git Tab
13. Click Push, above the noted dialog.
14. Return to your repository, and note a successful push by finding your files on GitHub's code tab.

Using Eclipse

1. In Eclipse, from the Eclipse Marketplace, install the eGit GitHub plugin.
2. Open your existing project.
3. Display the Git Repositories window by selecting Window > Show View > Other > Git > Git Repositories.
4. Click the Create a Git Repository button on the Git Repositories pane.
5. Make changes to your project and create a commit.
6. Push the changes to your default branch.
7. When asked for a remote, paste the URL you copied earlier.
8. Click next, and enter the branch name.

Why move to GitHub?

You may be wondering what this GitHub thing is all about and why you should use it. If this sounds like you, here are a few reasons to make GitHub your project's new home:

• Version control — Everything on GitHub is stored in Git, the best version control system around. Version control allows you to experiment and make mistakes in code without messing up your final product.
• Keep your code in one place — Whether you work on multiple computers or just want to get some important projects off your computer, GitHub is the perfect place to store your projects online.
• Collaboration — Once your code is on GitHub, you can invite others to work on your code with you, share it with the world, or send a link to a friend to help you debug a problem.

Moving your project from another version control system

If you are moving your project from another version control system, the steps are a bit different that uploading your project from your local machine. Because of this, we have a dedicated course for migrating your project to GitHub.

If you are moving your project from Mercurial, Subversion, or another Git platform, join the Migrating your project to GitHub course to migrate your project to GitHub.

Is your project using version control

If you aren't sure whether or not your code is under version control, it probably isn't. However, here are a few tests you can apply to know for certain:

• Can you view a history of the changes you have made?
• Can you easily roll back to a previous version of your project?
• Are you required to provide "messages" or "commits" when you make changes?

If none of these are true, your project isn't using version control.

Your project is already on your local machine

✨ Terrific! @AdityaGarg00 since you already have the project locally, you are almost ready to move it to GitHub.

To confirm: You have a project directory on your computer and you want to save it on GitHub.

• If this is correct, close this issue to signal you are finished with this step. I will open a new issue to show you how to optimize your repository for Git operations.

• If this is incorrect, please use the next drop-down to learn how to export your project to your local machine or join the Migrating your project to GitHub course to migrate your project to GitHub.

General instructions

There are many platforms that allow users to create and store projects. We can't cover them all, but we will do our best to cover the more common examples. First, let's cover general instructions:

• Export your project using the tools available on the current site. This will usually happen via a .zip, or some other compressed format, downloaded directly to your local machine
• Save the .zip file
• Extract the .zip file

Now let's talk about specific platforms:

Exporting from CodePen

From the main page of your CodePen project:

1. Click the Export button in the bottom right corner
2. Save the exported .zip file in your local directory
3. Extract the .zip file

Exporting from Glitch

From your Glitch project page:

1. Click the dropdown next to your project name in the top right corner
2. Select Advanced Options
3. Select Download Project
4. Save the exported file in your local directory
5. Extract the file
6. Rename the app folder as desired