Is there a way to control user commits on Bit Bucket - Online File Editing?

[Manjunatha Nagendra]

We have a requirement to restrict users to do the Code Check-Ins, if it is not associated with a Jira Ticket number. We have achieved this functionality already (using YACC pre-receive hook ) when users are trying to check-in from any tool outside the bit bucket (like Git Bash, Git Gui, Git extension, any IDE etc..). However the online edit from bit bucket is uncontrolled. Any one with write permission can do direct edit the file with out giving reference to any Jira ticket number on their commits. 

Could any one please let us know if there is a way, we can put restrictions for this online edit option in bit bucket, to follow some rules before pushing their commits.

Thanks in advance!

[jredmond]

Is this Bitbucket Cloud or Bitbucket Server?

Either way, you should be able to use branch permissions to restrict use of the online edit tool on a given branch.

[Julius Davies _bit-booster_com_]

Must be Server since YACC (Yet-Another-Commit-Checker) is a Bitbucket Server app.

I also maintain a competing (and free!) app that does similar things: Control Freak for Bitbucket Server.  Control Freak enforces commit checks on direct file edits in the UI.

[Manjunatha Nagendra]

@jredmond,  (we are using Bitbucket Server). Thanks for the reply, but the branch restriction is giving only 4 ways to prevent check-in which does not help much to my scenario. 

1. Prevent all changes

2. Prevent deletion

3. Prevent rewriting history

4. Prevent changes without a pull request

I want to allow users to check-in only when they use the Jira ticket number as part of their commits. The online edit does not allow any rules in settings. 

[Michael Heemskerk]

@Julius Davies _bit-booster_com_

Writing a repository hook that enforces the same logic for pushes, online edits and pull request merges should be trivial for 5.x. 

Just write a hook that implements PreRepositoryHook<RepositoryHookRequest> and check the RepositoryHookRequest.getTrigger() to only opt-in for pushes, online-edits and pull request merges.

If you already have a hook, it might be a couple of lines of code to change.

See the hooks and merge check guide for more details.