1. Bitbucket
  2. Public Issue Tracker
  3. master


Issue #8242 new

Add repo level configuration item to disable online editor (BB-9393)

Steve Muskiewicz
created an issue

Our development environment has some requirements as far as source code checking/formatting and test automation.

As such, we would like to avoid giving anyone the option of using the Bitbucket online editor to directly edit files in the remote repo.

Would it be possible to add a repo-level configuration setting to disable the online editor in all places (source tab, pull requests, any other source viewers) where it is normally available for that repo?

Comments (7)

  1. Brian Nguyen

    Hi Steve,

    Thanks for raising an issue with us. I have added this to our backlog, however so that we can better understand the issue, could you tell us how your environment protects agains checking/formatting and tests? For example, Do you run pre-commit hooks on each developers' machine?

    The reason why I am asking, is to see if this issue is actually part of a larger feature request.

    Cheers, Brian

  2. Steve Muskiewicz reporter

    Hmmm...I guess replying to this issue via email didn't actually work so here's the text of my reply again for the record:

    Hi Brian,

    Thanks for getting back so quickly.

    We're not actually using any pre-commit hooks or anything linked with Git, just some plugins in our Spring Tool Suite (ie. eclipse) IDE. (Checkstyle is one and there may be a couple others)

    Plus some of our developers are still learning Git so having something that actually changes a file contents on a remote branch is another potential point of confusion we'd like to avoid.

    Let me know if you have any other questions

    Cheers, -steve

  3. David Watson

    I'd like to second this request. Similarly, we have new developers who are just starting to learn Git, and we would prefer to remove any potential sources of confusion on workflow.

  4. Ricardo Machado

    I also would like to see this implemented. We have pre-push git hooks that, obviously, are not executed if the code is edited online. Some developers do that as a 'quick fix' and the best way to prevent it is to disable this functionality at all (on demand of course)

  5. Log in to comment