110

I have previously forked other people's repos on GitHub, and I have noticed that issues stay with the original repo, and that I can't file issues on the forked repo.

I now have the following task. I am working for a small business where development was being done by one of the principals on his personal account. He has amicably left the project, and we would like to migrate that project away from his personal account to a new "role" account on GitHub.

I would naturally fork the repo, in order to preserve the code history, but then I'll end up with a repo where we can't file new issues, which is quite undesirable.

How can I make a copy of this original repo into our new account, ideally still preserving code history, but be able to file new issues within this new account?

closed as off-topic by Thomas Owens Aug 26 '18 at 17:57

  • This question does not appear to be about software engineering within the scope defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.

  • I'm voting to close this question as off-topic because support for various products and services should be directed toward the appropriate support channels. – Thomas Owens Aug 26 '18 at 17:57
150

After a quick test, it is possible to attach an issue to your own fork of a repo. Here is what I did :

  • Fork a repo
  • Go to the Settings page of your fork.
  • Check the box next to Issues

You can now file issues on your own fork and they will not be placed in the main repo.

enter image description here

  • 1
    If you know what to do, sure. Why isn't it on by default? – Chaim Eliyah Nov 19 '17 at 23:35
  • 4
    @ChaimEliyah Because most forks on Github are made to create pull requests. It's important to make sure that bug reports end up in the original project, not in the clones where they would likely just be ignored. – Marc Schütz Jan 24 '18 at 12:01
13

There is also the option to transfer (ownership of) a repository from one account to another (e.g. from an ex-employee to an 'organization' account).

  • The "Transfer Ownership" button is at the bottom of the Settings page of the repository, in the "Danger Zone" section.
  • The current owner of the repository must have administrative privileges to the destination organization (though this could just be temporary).
2

This is an ancient question, and I would favor the approach that David P presents.

One more option is to remember that a local Git repository is an entire repository, complete with code history. You could just push it as another repository on GitHub, such that GitHub would have no idea the 2 were related. You still see your entire commit history.

This approach would cause you to loose any issue tracking history you have though. David P's approach is superior to mine, IMO.

Not the answer you're looking for? Browse other questions tagged or ask your own question.