How does renaming a Bitbucket git repository affect forked repositories?

Let’s say I have a Bitbucket git repository under This repository has been forked by several users and they regularly make pull-requests.

I now decide to rename the Bitbucket repository to Obviously I will need to update my local .git/config so that it points at the new URL.

  • Git pull on a remote server with an unknown tag
  • How to pull specific commit code from bitbucket-git
  • Deleted files from git cache do not reflect on the remote repository
  • Move project directory from to a new machine (git)
  • Remove the link to the upstream repository in Bitbucket
  • Fork public repository into private and receive public commits
  • Now, what happens to all the forks? How will the rename of my repository affect the ability of the contributors to make pull-requests?

  • git log - how to get an xml output
  • What is the difference between “renaming git branch to master” and “merging branch to master with -s ours option”?
  • hudson/jenkins keeps building the bad branch in git instead of the good one
  • Git Not Responding to Branch Changes
  • Fetch from origin in Bare Repository in Git does not create “remote branch”
  • Is there a way to disable vim's swap file warning?
  • One Solution collect form web for “How does renaming a Bitbucket git repository affect forked repositories?”

    Bitbucket handles this well. Your contributors will still be able to make pull requests. They will see the new name of your repository.

    (source: I just tested this with a small repository)

    Git Baby is a git and github fan, let's start git clone.