Is there a way to enable the 'Reject Force Push' hook for every repository in Stash?

I would like to be able to set the 'Reject Force Push' hook enabled for every repository we currently have, and also to have it set as the default for all repositories created in the future.

Is this possible, or would I need to do it manually in each existing project?

5 answers

1 accepted

1 vote
Answer accepted

Thanks, I came up with this Python 3 script which loops through the first 100 repositories and sets the hook to enabled:

import urllib.request, json

request = urllib.request.Request('')
base64string = 'base64_encoded username:password'
request.add_header("Authorization","Basic %s" % base64string)
result = urllib.request.urlopen(request)
jsonresult = json.loads('utf-8'))

for j in jsonresult['values']:
    enableHookUrl = "" %  (j['project']['key'], j['slug'])
    enableRequest = urllib.request.Request(enableHookUrl,data=b"")
    enableRequest.add_header("Authorization","Basic %s" % base64string)
    enableRequest.add_header("Content-Type", "application/json")
    enableRequest.get_method = lambda:'PUT'
    enableResult = urllib.request.urlopen(enableRequest)

I think this script would enable the hook on user repos as well. not sure you would want to do this.

There are REST API to enable hook:{projectKey}/repos/{repositorySlug}/settings/hooks/{hookKey}/enabled


  • {projectKey} -- one of you project
  • {repositorySlug} -- short name of repo
  • {hookKey} -- com.atlassian.stash.stash-bundled-hooks:force-push-hook (in your case)

From description:

Enable a repository hook for this repositories and optionally applying new configuration.

The authenticated user must have REPO_ADMIN permission for the specified repository to call this resource.

You can also use REST to get list of all repos/projects in your Stash.

As an alternative to the above, I have added a ruby version here with a few elements commented out. This one will only set the hook on the main repos, not users forks or other user repos as denoted by the '~' in the key. There is a line at the begining for retriving the repos details but I had trouble with this as it did not appear to be returning proper json to my ruby script (even though it is responding with 'application/json' content) but this is likely my bad coding rather than stash. enjoy

require 'net/http'
require 'open-uri'
require 'rubygems'
require 'json'

#content = open("").read
#json = JSON.parse(content)

jsonFile ='repos.json')
json = JSON.parse(jsonFile)

json['values'].each do |value|
        puts value['id']
        if value['project']['key'].include? '~'
#               puts "This is a private project"
#       elsif value['origin']['project']['isPersonal'] == false
#                puts "key is: #{value['origin']['project']['key']}"
#                puts "repo is: #{value['origin']['slug']}"
#               puts "key is: #{value['project']['key']}"
#               puts "repo is: #{value['slug']}"
                hookURL = "{value['project']['key']}/repos/#{value['slug']}/settings/hooks/com.atlassian.stash.stash-bundled-hooks:force-push-hook/enabled"
#               puts hookURL

                uri = URI.parse(hookURL)
                http =, uri.port)
                request =
                request.basic_auth("user", "pass")
                response = http.request(request)
                puts response

This is a bit late, but, I just saw this - it might help others:

You can use Stash Command Line Interface (CLI) action enableHook and combine that with runFromRepositoryList to hit everything. 

stash --action runFromProjectList --common "--action runFromRepositoryList --project @project@ --common \"--action enableHook --hook com.atlassian.stash.stash-bundled-hooks:force-push-hook --project @project@ --repository @repository@\" "

I have used an open source python plugin written for Stash API:

import stashy
stash = stashy.connect("http://localhost:7990/stash", "admin", "admin")


You can easily loop through the projects and the repos under those projects. After that, turning this script into a cron job seems to be the only viable solution.



Suggest an answer

Log in or Sign up to answer
Community showcase
Published Mar 14, 2019 in Bitbucket Pipelines

Building a Bitbucket Pipe as a casual coder :  #!/bin/bash source "$(dirname "$0")/" enable_debug extra_args="" if [[ "${DEBUG}" == "true" ]]; then extra_args="--verbose" fi # mandatory variables R...

288 views 0 12
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