| com.atlassian.bitbucket.hook.repository.RepositoryHookRequest | 
Request that is provided to repository-hook modules  for inspection
 (pre-hooks and
 post-hooks). The request describes the
 ref changes that are about to be made (pre-hooks), or that have just been made
 (post-hooks).
 
 A request is marked as a dry-run request when the proposed ref changes
 need to be quickly verified, for instance to determine whether a button in the web UI should be enabled.
 Hooks that are called with a dry-run request should avoid expensive checks and operations.
| Public Methods | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Retrieves any additional context that was supplied to the request. | |||||||||||
Retrieves any additional context that was supplied to the request. This context is intended to allow plugin developers to implement their own behavior around ref-changes. As a result, its contents are unspecified; they depend on the installed plugins.
 On dry runs, the context will always be empty.
empty for some dry-run requests where the
         target hash is not yet known because the relevant commit hasn't been created yet. As an example, this is
         the case for merge requests. In these cases, the specialized request type should
         provide sufficient information about the proposed change. For MergeHookRequest, this would be
         getFromRef() and getToRef().
true if this hook is a dry-run request, otherwise false