I just forked a repository to work on a project, and the original repository had around 10 open issues.

So, as soon as I forked the repository, I can see that these issues are not available on my version of the project (forked). Is there any way to fork a repository but also keep the original issues?

CodePudding user response：

Except if you want to have your own specific workflow, there is no real need to have the issues all duplicated in your fork.

• You will indeed work with the issues of the upstream repository.
• You still can refer to the original issues with #idIssue.
• You will push your branch and create a pull request.
• When your PR will be created, the issues referenced will be automatically linked to your PR.
• Once the PR will be merged, the issue will be closed (automatically -- if you used the keyword 'Fixes' -- or manually by a maintainer).

All the projects using Github are working like that and that is good enough (until you want to do a hard fork because you really don't want to contribute to the upstream project)