Clone the forked repository to your computer

[hydrolet]

Why this task matters

Cloning pulls the Threadbare fork from GitHub onto your machine, creating a local Git repo you can edit.

Steps

1. Create a folder for your StoryQuest. Navigate to a location like Documents or Desktop. Right-click and select New > Folder. Name it something simple, like storyquest (no spaces or capital letters).

2. Get the repository URL. Open the repository on GitHub and look for the green dropdown box that says Code. Copy the HTTPS URL to your clipboard. It will look something like:

   https://github.com/OrgName/threadbare-yourquest.git
   

3. Tell Git where to find the new folder. There are two ways to do this:

   1. Use the cd (change directory) command: Open Git and type:

      cd folder-name
      

      to go into the new folder. For example:

      cd C:/Users/YourName/Desktop/StoryQuest
      

      Write this address down for future use. Tip: You can also type dir to list the contents of the current folder you are in.
   2. Use the Git folder short-cut

• (Windows-only): Right-click inside your new StoryQuest folder. Choose "Show more options". Select Open Git Bash Here. This opens a Git terminal directly in that folder.
• (macOS): Control-click (or right-click) the folder and choose New Terminal at Folder (or Open in Terminal)

4. Clone the repository into your folder. Use this command:

   git clone https://github.com/OrgName/threadbare-yourquest.git
   

   Git will clone the repository as a new folder inside the one you made. You can just use the cd command once more to navigate into this folder.

5. Check your status. Run:

   git status
   

   You should see: On branch main and nothing to commit.

✅ Done! You now have a working copy of the project ready to open in Godot.

Video

[wjt]

git clone https://github.com/OrgName/threadbare-yourquest.git .

I think cloning directly into the current directory (.) is a bad idea because if you forget to cd to another directory, then you clone into your home directory, and suddenly git wants to track every file in your home directory as part of Threadbare. This is not hypothetical: I've received an email from a learner where this appears to have happened.

I think it would be much less error-prone to do this:

# Clone to a specific directory that doesn't exist yet
git clone https://github.com/OrgName/threadbare-yourquest.git ~/Desktop/storyquest

# Now `cd` to that directory
cd ~/Desktop/storyquest

(As an aside I think the Markdown notation with three backticks, putting the commands in their own paragraph, is much clearer than having them inline. The command with a trailing . is a good example because you have two dots, one inside and one outside the code block.)

[wjt]

Or even don't specify a target path as the second parameter to git clone. The default will be threadbare which I think is fine?

[wjt]

I have adjusted the formatting to use fenced blocks (triple-backticks) to put commands that should be typed into their own clearly-delineated paragraphs.