Purpose and valid values for key "triggerIds" in a REST call to "Create/update a hook script"

[landro]

I use the following REST call to create a repository hook, which works fine. https://developer.atlassian.com/server/bitbucket/rest/v810/api-group-repository/#api-api-latest-projects-projectkey-repos-repositorieslug-hook-scripts-scriptid-put

I couldn't figure out what effect the list of strings has on the repository hook. 
“triggerIds”: [ “<string>” ]
Apparently this has no effect at all as the result is the same regardless of the strings I use. Each time you execute a push, the hook is executed.

[Jimmy Lowe]

No answer but have the exact same question. We have a pre-commit hook that is firing on merges which isn't desired and wondering if triggerid's might be the most correct way to get the hook to only execute on a regular commit.