1

I am currently working on a project in which I have the reporter rights (not allowed to push etc.). Unfortunately I did not create a fork, but cloned the original one on my machine and now I am struggling with the idea how to publish it to get feedback.

Since I can't push to the original repository, I thought I could just create a new repository and change the remote, but it seems to me that I will lose the connection to the original one and can't pull anymore to update the changes. Will setting different push remote and different pull remote be enough to solve this problem ?

What would be the reasonable scenario to follow in my case ?

prosoitos
  • 6,679
  • 5
  • 27
  • 41
bdskfsdk321dsad3
  • 113
  • 1
  • 2
  • 9
  • Yes, that will solve your problem. You can choose where to push and where to pull from – prosoitos Oct 20 '19 at 20:02
  • The only downside of this strategy though is that you won't be able to submit a PR to the original project that easily. So a better solution might be to create a fork of that project, download it to your local computer, then merge all the changes that you had made to your clone – prosoitos Oct 20 '19 at 20:03
  • What do you mean by "change the remote"? You can have multiple remotes. You certainly don't need to `remote remove origin` and add the new remote under the name `origin`. Let origin continue to be the name of the current remote, and add your new remote with a different name. – William Pursell Oct 21 '19 at 03:33

1 Answers1

1

Working from a fork of the original project would have been the best strategy since it would allow you to easily submit PR (pull requests) to it. So the best is to get back to this classic contribution setting:

  1. Fork the original project

  2. Set this fork as the remote for the project you have on your computer (the clone you made from the original project and on which you worked)

cd <path-to-your-local-repository>
git remote add origin <address-of-your-fork>
  1. Fetch the content of that fork (to get updates that were made in the original project since you cloned it)
git fetch
  1. Merge what you fetched with your local project
git merge origin/master

Note that steps 3 and 4 can be achieved in one command with: git pull.

  1. Push to origin (this will push your local work to your fork)
git push -u origin master

(Replace master by the name of your branch if you are working on a brach).

  1. Set the original project as upstream (so that you can pull or fetch the changes to keep your fork up to date with the original project)
git remote add upstream <address-of-original-project>

Now you can push to your fork (for feed-back), you can pull or fetch from the original project (to keep up to date), and you can easily submit PR to the original project.

prosoitos
  • 6,679
  • 5
  • 27
  • 41