gh-pages: Failed to get remote.origin.url (task must either be run in a git repository with a configured origin remote or must be configured with the "repo" option)

I just had the same issue and was able to resolve it. Here’s what I did:

In my terminal, when I ran git remote -v, I did not see any remote’s withe the name ‘origin’. So, I added one with git remote add origin <url>, with the URL of my repository on Github.

My other remote pointed to the same url, it just wasn’t called ‘origin’.

Then, when I ran ‘npm run deploy’ everything worked. I hope this helps, though it’s a year after you last posting.

you should add remote url for your project , then run gh-pages -d build.

I just had the same issue and was able to resolve it. Here’s what I did:

In my terminal, when I ran git remote -v, I did not see any remote’s withe the name ‘origin’. So, I added one with git remote add origin <url>, with the URL of my repository on Github.

My other remote pointed to the same url, it just wasn’t called ‘origin’.

Then, when I ran ‘npm run deploy’ everything worked. I hope this helps, though it’s a year after you last posting.

Thank you so much you saved me

If u won’t to add origin repo, just change command "deploy": "gh-pages -d build" to "deploy": "gh-pages -d build -r <repo_url>"

Also to check all available flags just run npx gh-pages --help

I just had the same issue and was able to resolve it. Here’s what I did:

In my terminal, when I ran git remote -v, I did not see any remote’s withe the name ‘origin’. So, I added one with git remote add origin <url>, with the URL of my repository on Github.

My other remote pointed to the same url, it just wasn’t called ‘origin’.

Then, when I ran ‘npm run deploy’ everything worked. I hope this helps, though it’s a year after you last posting.

Bruh!! This is still helping people to this day!!!

In my case the problem was solved by renaming my remote control by ‘origin’ 👍😁

I get the same error. I followed the instructions on https://github.com/facebookincubator/create-react-app/blob/master/packages/react-scripts/template/README.md#github-pages I have added “homepage”: “https://carpben.github.io/fccLeaders/” to my package.json. And I have remote set on my git (When I do push it logs “everything up to date”.

The terminal I’m using is bash on ubuntu on Windows. And it might be the issue. I used bash for this project till now. However, when I try moving to PowerShell and give the command npm run build it says it doesn’t recognise react-script. I guess it is because create-react-app installed the bash version not the windows version. Any diagnosis or possible solutions?

My origin was set up correctly, but because the repository folder was copied from another machine, deploying didn’t work. I deleted the repository and cloned it again, and the issue was fixed.

Thank you, this works for me. Really appreciate!

Same problem.

remote add origin <url> did not work for me cause there’re already origin urls in git remote -v.

Finally I changed the owner of the folder and it solved.

I have the same issue I have remote name origin and still getting this error, Failed to get remote.origin.url (task must either be run in a git repository with a configured origin remote or must be configured with the “repo” option).

Here is my package.json file { “name”: “testapp”, “version”: “0.1.0”, “homepage”: “https://dhanur350.github.io/testapp”, “private”: true, “dependencies”: { “@testing-library/jest-dom”: “^5.16.5”, “@testing-library/react”: “^13.4.0”, “@testing-library/user-event”: “^13.5.0”, “gh-pages”: “^5.0.0”, “react”: “^18.2.0”, “react-dom”: “^18.2.0”, “react-scripts”: “5.0.1”, “web-vitals”: “^2.1.4” }, “scripts”: { “start”: “react-scripts start”, “predeploy”:“npm run build”, “deploy”: “gh-pages -d build”, “build”: “react-scripts build”, “test”: “react-scripts test”, “eject”: “react-scripts eject” }, “eslintConfig”: { “extends”: [ “react-app”, “react-app/jest” ] }, “browserslist”: { “production”: [ “>0.2%”, “not dead”, “not op_mini all” ], “development”: [ “last 1 chrome version”, “last 1 firefox version”, “last 1 safari version” ] } }

Any suggestions to fix this…??

I just had the same issue and was able to resolve it. Here’s what I did:

In my terminal, when I ran git remote -v, I did not see any remote’s withe the name ‘origin’. So, I added one with git remote add origin <url>, with the URL of my repository on Github.

My other remote pointed to the same url, it just wasn’t called ‘origin’.

Then, when I ran ‘npm run deploy’ everything worked. I hope this helps, though it’s a year after you last posting.

This really worked thanks bro!!

I renamed the remote name as origin and then my problem get solved.

You are like coming from heaven Thank all of you guys my problem is solved problem =>failed to get remote.origin.url solution => git remote add origin <url> then npm run deploy

I just had the same issue and was able to resolve it. Here’s what I did:

In my terminal, when I ran git remote -v, I did not see any remote’s withe the name ‘origin’. So, I added one with git remote add origin <url>, with the URL of my repository on Github.

My other remote pointed to the same url, it just wasn’t called ‘origin’.

Then, when I ran ‘npm run deploy’ everything worked. I hope this helps, though it’s a year after you last posting.

This really worked for me