Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-4204

Force push and synchonize->discard should go in the audit log

XMLWordPrintable

    • 9
    • 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.

      Both force push and synchronize->discard for forks with fork syncing enabled (which I'm assuming is basically just a force push under the scenes anyway) are dangerous operations that can permanently alter the version history in unrecoverable ways and which don't show up in the commit log.

      It would be useful if the occurrence of such an event and the user who performed either of the actions was listed in the audit log.

      We had a problem recently with someone incorrectly discarding changes when resolving a fork sync issue and we have been unable to track down who performed it so we can talk through the impact that had and provide more training.

            Unassigned Unassigned
            andrew.milne1 andrew.milne1
            Votes:
            15 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated: