This repository has been archived by the owner on Oct 17, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 6
Reference_Format
mattt edited this page Aug 17, 2020
·
2 revisions
Normalization options for reference lookup.
public enum Format
No particular normalization.
case normal
Control whether one-level refnames are accepted
(i.e., refnames that do not contain multiple /
-separated components).
case allowOneLevel
Those are expected to be written only using
uppercase letters and underscore (FETCH_HEAD
, ...)
Interpret the provided name as a reference pattern for a refspec (as used with remote repositories).
case refspecPattern
If this option is enabled,
the name is allowed to contain a single *
()
in place of a one full pathname component
(e.g., foo/<star>/bar
but not foo/bar<star>
).
Interpret the name as part of a refspec in shorthand form
so the ONELEVEL
naming rules aren't enforced
and 'master' becomes a valid name.
case refspecShorthand
Generated at 2020-09-02T17:06:43+0000 using swift-doc 1.0.0-beta.4.
Types
- Blob
- Branch
- Commit
- Credentials
- Error
- Message
- Note
- Object
- Object.ID
- Reference
- Reference.Format
- Remote
- Remote.Fetch
- Remote.Fetch.Configuration
- Remote.Fetch.TagFollowing
- Repository
- Repository.Attributes
- Repository.Attributes.Value
- Repository.Checkout
- Repository.Checkout.Configuration
- Repository.Checkout.ConflictResolution
- Repository.Checkout.Strategy
- Repository.Clone
- Repository.Clone.Configuration
- Repository.Clone.Local
- Repository.Head
- Repository.Index
- Repository.Index.Entry
- Repository.Index.Stage
- RevisionSortingOptions
- Signature
- Tag
- Tag.Annotation
- Tree
- Tree.Entry