-
Notifications
You must be signed in to change notification settings - Fork 39.7k
SCM: Support scmResourceState in when clauses #86180
Copy link
Copy link
Closed
Labels
apiapi-finalizationauthor-verification-requestedIssues potentially verifiable by issue authorIssues potentially verifiable by issue authorfeature-requestRequest for new features or functionalityRequest for new features or functionalityinsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code Insiderson-release-notesIssue/pull request mentioned in release notesIssue/pull request mentioned in release notesscmGeneral SCM compound issuesGeneral SCM compound issuesverification-neededVerification of issue is requestedVerification of issue is requestedverifiedVerification succeededVerification succeeded
Milestone
Metadata
Metadata
Assignees
Labels
apiapi-finalizationauthor-verification-requestedIssues potentially verifiable by issue authorIssues potentially verifiable by issue authorfeature-requestRequest for new features or functionalityRequest for new features or functionalityinsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code Insiderson-release-notesIssue/pull request mentioned in release notesIssue/pull request mentioned in release notesscmGeneral SCM compound issuesGeneral SCM compound issuesverification-neededVerification of issue is requestedVerification of issue is requestedverifiedVerification succeededVerification succeeded
See also #27946 for a related request/question.
The SCM API described here allows you to conditionally add commands to the SCM menus based on the
scmProviderandscmResourceGroup, but not based on thescmResourceState.Conditions on the
scmResourceStatewould be valuable for mercurial extensions (which differentiates between behavior for modified files vs. added files vs. untracked files) without needing to use separate groups for all of them.