Pull request without forking?

Question

If you don't have access to create branches on that repository, there is no way to create a pull request without forking.

Once your pull requests are accepted, you can safely delete the repo.

Afterwards, simply clone directly from the original upstream repo.

If you have other pull requests to make, then you should make them in their own respective branch, which means you can safely delete the branch you made to manage an accepted pull request (as in "My pull request has been merged, what to do next?")

By definition, a pull request involves a fork unless you have commit access to the destination repository. You can do a couple of things, though:

1. If you do have commit access, create a branch and make your pull request against the new branch.
2. Post your patch in the body of an issue. This isn't really the GitHub way, but it certainly works.
3. Fork a repository, create a pull request, and then delete the fork once the pull request is merged or declined.

If you're just trying to avoid keeping repositories around that you aren't actively using, I personally suggest option #3. It sticks to the accepted GitHub workflow without cluttering up your dashboard.

github supports Shared Repository Model

The Shared Repository Model is more prevalent with small teams and organizations collaborating on private projects. Everyone is granted push access to a single shared repository and topic branches are used to isolate changes.

Pull requests are especially useful in the Fork & Pull Model because they provide a way to notify project maintainers about changes in your fork. However, they're also useful in the Shared Repository Model where they're used to initiate code review and general discussion about a set of changes before being merged into a mainline branch.