Any consequence to the upstream remote repo and other repos if I remove my forked repo?

[Horinius]

I have followed the "Fork a repo" tutorial (shown in the link below) up to the end:
https://confluence.atlassian.com/display/BITBUCKET/Fork+a+Repo%2C+Compare+Code%2C+and+Create+a+Pull+Request

That means I had commited a change and submitted a pull request which was accepted.

But nothing is written about what we should do to the forked repo after. So I'm wondering what would happen if I remove my forked repo. Is there any consequence to the main branch (you call it "upstream remote repo", right?) if my forked repo is removed? Well, I would bet nothing bad would happen, but I'd better ask.

When I look at graphical representation of all these forks and pull requests, every fork and pull/merge related to a repo is drawn as a continuous curve. If I remove my repo, and when somebody else is looking at the graphical representation around my pull request, will it appear as if a pull existed out of nowhere? ("nowhere" means a discontinuous curve without any previous fork).

So, what really would happen to other repos if I delete my forked repo?

Thanks

[Seth · Accepted solution]

The repo itself would be completely unaffected by the removal of a fork. I do not know how bitbucket will render the pull request after the fork is deleted, but the integrity of the git/hg repository should remain intact.

[Horinius]

Another user told me that pull requests are not affected.