Home > Net >  Why am I pushing to one repository but the Pull Request is created in another?
Why am I pushing to one repository but the Pull Request is created in another?

Time:10-28

I am working on this public repository called tallyfor/flow. As you see, it is a fork of nodename/flow which in turn is a fork of the original fmnoise/flow.

Locally, I created a branch called add-ci-to-automatically-publish-packages and added a ci.yml file (Continuous Integration effort).

After executing the command below to create a Pull Request:

git push origin add-ci-to-automatically-publish-packages

Things seemed to be correct about the "address" where the Push would go:

~/projects/flow on add-ci-to-automatically-publish-packages
➜  git remote -v
origin  [email protected]:tallyfor/flow.git (fetch)
origin  [email protected]:tallyfor/flow.git (push)

However, something weird happens, since my Pull Request does not go to the expected repository. Instead of going to tallyfow/flow, the Pull Request goes to nodename/flow - see the PR here.

Why does this happen? How can I make the changes on tallyfor/flow?

CodePudding user response:

Answer (which makes no sense without the background)

It seems likely that you're using one of the automated setups, where you (or someone you work with) has set things up so that your git push to your fork triggers a GitHub Action that creates a PR from your fork to its upstream. That's not something Git does, that's something GitHub is doing. If you don't want it to do that, stop telling it to do that.

  • Related