• 5
    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Currently fork syncing stops working if someone does a force push to the original repo. It seems very reasonable for fork syncing to stop working if that happens. However, the users who are depending on fork syncing should be notified via email and the inbuilt message box that it has stopped. It should not silently stop working.

          Form Name

            [BSERV-4495] Fork sync should notify when it stops syncing

            I agree with the general approach to notifications for any reason and suggest to use the same messaging mechanism that we already have in place for when fork syncing stops due to removed permissions:

            Hendrik (Inactive) added a comment - I agree with the general approach to notifications for any reason and suggest to use the same messaging mechanism that we already have in place for when fork syncing stops due to removed permissions:

            I would generalize this to say email a notification list for any reason that the fork syncing stalls.

            Chuck Burgess added a comment - I would generalize this to say email a notification list for any reason that the fork syncing stalls.

              Unassigned Unassigned
              88e1ccbd67c9 Stephan Hoermann
              Votes:
              24 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated: