public interface RepositoryRefsChangedEvent
RepositoryRefsChangedEvent
listeners will be notified when any
sub-events are published. As a result, listening for this event is the
best way to be aware of repository changes.
Modifier and Type | Method and Description |
---|---|
Collection<RefChange> |
getRefChanges()
Retrieves a collection of the
changed refs . |
Repository |
getRepository()
Retrieves the repository in which refs were changed.
|
ApplicationUser |
getUser()
Retrieves the user who triggered the ref changes, if available.
|
@Nonnull Collection<RefChange> getRefChanges()
changed refs
.
Note: While the returned collection will never be null
, it may be empty. For example, a
remotely merged pull request
will have an empty set of changes.
@Nonnull Repository getRepository()
changed refs
for a
single event will always be in the same repository.@Nullable ApplicationUser getUser()
In most contexts, the user will be set. However, some changes may happen in contexts where no context user is available. For example, custom plugins may perform automated processing outside of a user context and raise change events based on the processing performed. Callers are encouraged to check for and handle the case where there is no user available.
null
if the change happened due to background processing or in another
context where no user is availableCopyright © 2019 Atlassian. All rights reserved.