Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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?

share|improve this question
Hi Tom, please read our FAQ thoroughly, especially the Can I use a signature or tagline? and Other people can edit my posts?! sections. I've reviewed the edits, and I don't see anything wrong there, salutations, taglines and such are generally considered noise, we prefer to keep all posts as concise and to the point as possible. If you would like to further discuss the issue, feel free to ask a question about it on our Meta site. – Yannis Dec 14 '12 at 19:55
I'm voting to close this question as off-topic because it is about the use and configuration of a third party web site, but is too old to migrate to WebApps.SE. – user40980 Feb 5 at 2:06
up vote 64 down vote accepted

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 (duh!)
  • 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. Pretty straightforward, isn't it?

share|improve this answer
Thank you. It should have been obvious, but two of us missed it entirely. – Tom Swirly Dec 14 '12 at 19:25

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).
share|improve this answer

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.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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