java.lang.Object | ||
↳ | java.lang.Enum<E extends java.lang.Enum<E>> | |
↳ | com.atlassian.bitbucket.scm.ScmFeature |
Enumerates optional features an SCM can support.
Enum Values | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
ScmFeature | ARCHIVE | Indicates the SCM supports streaming archives . |
|||||||||
ScmFeature | BULK_COMMITS | Indicates the SCM supports bulk commit retrieval . |
|||||||||
ScmFeature | BULK_CONTENT | Indicates the SCM supports bulk content retrieval . |
|||||||||
ScmFeature | COMMAND_BUILDERS | Indicates the SCM supports builders . |
|||||||||
ScmFeature | COMPARE | Indicates the SCM provides a command factory
to compare refs. |
|||||||||
ScmFeature | CROSS_REPOSITORY | Indicates the SCM supports cross-repository operations. | |||||||||
ScmFeature | EDIT_FILE | Indicates the SCM supports file edit operations. | |||||||||
ScmFeature | FORK | Indicates the SCM supports forking its repositories. |
|||||||||
ScmFeature | HOOKS | Indicates the SCM provides a handler factory to apply repository-level hooks. |
|||||||||
ScmFeature | INTEGRITY_CHECKS | Indicates the SCM supports integrity checks | |||||||||
ScmFeature | LAST_MODIFIED | Indicates the SCM supports streaming the last modification
for files. |
|||||||||
ScmFeature | MERGE | Indicates the SCM supports merging branches . |
|||||||||
ScmFeature | MERGE_STRATEGIES | Indicates the SCM supports selectable merge strategies. | |||||||||
ScmFeature | MIRRORS | Indicates the SCM supports mirroring repositories |
|||||||||
ScmFeature | PULL_REQUESTS | Indicates the SCM provides a command factory
to create, view and merge pull requests . |
|||||||||
ScmFeature | REFS | Indicates the SCM provides a command factory to create
branches and tags . |
|||||||||
ScmFeature | SIGNED_OBJECTS | Indicates the SCM supports retrieving
signed objects . |
|||||||||
ScmFeature | UPDATE_DEFAULT_BRANCH | Indicates the SCM supports updating the default branch
in its repositories. |
Public Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
[Expand]
Inherited Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
From class
java.lang.Enum
| |||||||||||
From class
java.lang.Object
| |||||||||||
From interface
java.lang.Comparable
|
Indicates the SCM provides a command factory
to compare refs.
Note: SCMs may support comparing refs cross-repository
, but they are not
required to do so.
Indicates the SCM supports cross-repository operations. This feature applies to:
Implementing these features in a cross-repository manner may involve substantial additional complexity, so SCMs are free not to. When this feature is not supported, providing a secondary repository on commands likecommits
or opening a pull request
between two
repositories will fail.Indicates the SCM supports forking
its repositories.
SCMs which do not support forking will not support cross-repository
operations,
but just because forking is supported does not imply cross-repository support. The complexity of
cross-repository operations can be substantially higher than the complexity of creating forks, for some
SCMs, and forks can still offer value (for example, a sandboxed place to work) even if cross-repository
operations are not possible.
Indicates the SCM provides a handler factory
to apply repository-level hooks.
Indicates the SCM supports streaming the last modification
for files.
Indicates the SCM supports merging branches
.
Note: SCMs may support cross-repository
merges, merging a branch from one
repository to a target branch in another, but they are not required to do so.
Indicates the SCM supports selectable merge strategies. Only SCMs which support merge commands
and/or pull requests
should mark this feature as supported.
Generally an SCM should support at least two strategies if this feature is enabled since, with only a single strategy, the strategy isn't actually selectable. But the only requirement of this feature is that the SCM must support at least one strategy.
Indicates the SCM provides a command factory
to create, view and merge pull requests
.
Note: SCMs may support cross-repository
pull requests, merging commits from
one repository into another, but they are not required to do so.
Indicates the SCM provides a command factory
to create
branches
and tags
.
Indicates the SCM supports updating the default branch
in its repositories.