Great question, and I have no idea! This is the first repo I’ve seen issues doing the built-in GitHub copy, and it’s also the first one I’ve built out with GitHub actions. Maybe that’s the culprit?

But don’t give up yet, you can still download this repo and upload it to your own GitHub where you can make changes.

Go to the source repo and download the Zip file.

Unzip the file on your computer.

Create an empty repo in your GitHub — Top right + → New Repo, name whatever you’d like, then click create.

I was initially going to upload the files via the GitHub webpage, but it won’t permit the hidden files (those starting with a period) to be uploaded, so we’ll need to use git for this next step.

Head into your repo. It won’t have any files yet, and it’ll display a “quick setup” section at the top with an SSH address in it. Copy that.

On your computer, create a folder somewhere. This will be the root of the repo. I usually use the same name as my GitHub repo to keep me sane(ish).

Unzip the files you downloaded, and put them into this folder. Make sure to grab the files starting with period — the .gitignore file and .github folder.

Run git init to initialize the repo. Then git add . to add all files to the staging area for a commit. Then git commit -m "adding files" to create a commit and put all the staged files into it. You should see all the files, including the ones with a leading period. If you don’t, make sure you staged them in this folder properly.

Then git remote add origin plus the cloning string we downloaded from your new repo. You can see what mine looks like below. Then we’ll push all our changes to the repo with git push -u origin master.

Refresh your GitHub repo page and you should see all the replicated files there. And now that you’ve done all that, you can see why I prefer the native GitHub “clone repo” button. I wish it worked here!

I hope that helps! If you’re more comfortable with git you could also clone the repo to your local computer, than copy files to your new repo that way. I chose this way because it’s available to everyone, regardless of previous skills.

Good luck!

DevNetSecOps engineer, consultant, business owner, Pluralsight author. Fascinated with computer security and privacy policy. Teacher. They/Them.