GitRefUpdateStatus Enum

Definition

Namespace:

Microsoft.TeamFoundation.SourceControl.WebApi

Assembly:

Microsoft.TeamFoundation.SourceControl.WebApi.dll

Represents the possible outcomes from a request to update a ref in a repository.

public enum GitRefUpdateStatus

type GitRefUpdateStatus = 

Public Enum GitRefUpdateStatus

Inheritance

Enum

GitRefUpdateStatus

Fields

Name	Value	Description
Succeeded	0	Indicates that the ref update request was completed successfully.
ForcePushRequired	1	Indicates that the ref update request could not be completed because part of the graph would be disconnected by this change, and the caller does not have ForcePush permission on the repository.
StaleOldObjectId	2	Indicates that the ref update request could not be completed because the old object ID presented in the request was not the object ID of the ref when the database attempted the update. The most likely scenario is that the caller lost a race to update the ref.
InvalidRefName	3	Indicates that the ref update request could not be completed because the ref name presented in the request was not valid.
Unprocessed	4	The request was not processed
UnresolvableToCommit	5	The ref update request could not be completed because the new object ID for the ref could not be resolved to a commit object (potentially through any number of tags)
WritePermissionRequired	6	The ref update request could not be completed because the user lacks write permissions required to write this ref
ManageNotePermissionRequired	7	The ref update request could not be completed because the user lacks note creation permissions required to write this note
CreateBranchPermissionRequired	8	The ref update request could not be completed because the user lacks the permission to create a branch
CreateTagPermissionRequired	9	The ref update request could not be completed because the user lacks the permission to create a tag
RejectedByPlugin	10	The ref update could not be completed because it was rejected by the plugin.
Locked	11	The ref update could not be completed because the ref is locked by another user.
RefNameConflict	12	The ref update could not be completed because, in case-insensitive mode, the ref name conflicts with an existing, differently-cased ref name.
RejectedByPolicy	13	The ref update could not be completed because it was rejected by policy.
SucceededNonExistentRef	14	Indicates that the ref update request was completed successfully, but the ref doesn't actually exist so no changes were made. This should only happen during deletes.
SucceededCorruptRef	15	Indicates that the ref update request was completed successfully, but the passed-in ref was corrupt - as in, the old object ID was bad. This should only happen during deletes.