Suggested change to PreRepositoryHook

My plugin is reporting findings from the commit messages when commits are pushed. It does not necessarily have to be findings that should reject the commit from being pushed. It can be information, or warnings, that should just be communicated.

If I understand correctly I should, from BBS 6.0, implement this class instead:

If I understand correctly, it can only report feedback with RepositoryHookResult and only when commits are rejected. It cannot report back a text message regarding valid accepted commits.

I would suggest that being changed. That was pretty much the only reason that I started working on this plugin.

A quick googling did not tell my how to make such a request!

1 answer

1 accepted

I haven't ported my own hook to the new BB 6 approach, but from clicking around the javadocs a little, I think you can write messages using the 2nd parameter "T request" of the preUpdate() call.    This "request" param will probably implement RepositoryHookRequest, in which case you can call request.getScmHookDetails().out().

Suggest an answer

Log in or Join to answer
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

710 views 0 4
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot