Issue #8369 resolved

"follow" leaks repository information when creating private repo

Scott Lawrence avatarScott Lawrence created an issue

Using the web interface to fork an existing repository to a private copy, other users receive notices containing the name of the new repository.

In my case, I forked from the team lindenlab/viewer-release to a repo in another hidden team account. Users not in either team received notices containing the name of the hidden team and the newly created hidden repository. Since they could not see either the team in which the repository was created, nor the resulting repo, they should not have received any notice.

Comments (6)

  1. Marcus Bertrand

    Can you confirm if the users who received the notification were followers of the repository that was forked? In other words, did Bitbucket appear to alert only the followers of the repo that the fork was from xx -> yy?

    Or, did a different set of users receive the notification? Once we understand who got the notice, and shouldn't have, we can start work on ensuring we are giving the right information to the right people.

  2. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.