|↳||java.lang.Enum<E extends java.lang.Enum<E>>|
Enumerates optional features an SCM can support.
|ScmFeature||BULK_CONTENT||Indicates the SCM supports
|ScmFeature||COMMAND_BUILDERS||Indicates the SCM supports
|ScmFeature||COMPARE||Indicates the SCM provides a
|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
|ScmFeature||HOOKS||Indicates the SCM provides a
|ScmFeature||INTEGRITY_CHECKS||Indicates the SCM supports integrity checks|
|ScmFeature||LAST_MODIFIED||Indicates the SCM supports streaming the
|ScmFeature||MERGE||Indicates the SCM supports
|ScmFeature||MERGE_STRATEGIES||Indicates the SCM supports selectable merge strategies.|
|ScmFeature||MIRRORS||Indicates the SCM supports
|ScmFeature||PULL_REQUESTS||Indicates the SCM provides a
|ScmFeature||REFS||Indicates the SCM provides a
|ScmFeature||UPDATE_DEFAULT_BRANCH||Indicates the SCM supports
|From class java.lang.Object|
Indicates the SCM supports cross-repository operations. This feature applies to:
commitsor opening a
pull requestbetween two repositories will fail.
Indicates the SCM supports file edit operations.
Indicates the SCM supports
forking its repositories.
SCMs which do not support forking will not support
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 supports integrity checks
Indicates the SCM supports streaming the
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.