{0} Commit & PushCommit & Push Changes{0} Commit & SyncCommit & Sync Changes{0} CommitCommit to New Branch & Push ChangesCommit to New Branch & Sync ChangesCommit Changes to New BranchCommit ChangesCommitting & Pushing Changes...Committing & Synching Changes...Committing to New Branch & Pushing Changes...Committing to New Branch & Synching Changes...Committing Changes to New Branch...Committing Changes...{0} ContinueContinue RebaseContinuing Rebase...Publish Branch{Locked="Branch"}
Do not translate "Branch" as it is a git termPublishing Branch...{Locked="Branch"}
Do not translate "Branch" as it is a git term{0} Sync Changes{1}{2}{0} Publish Branch{Locked="Branch"}
Do not translate "Branch" as it is a git termCommitSynchronizing Changes...Missing or invalid credentials.NoAsk Me LaterWould you like Azure Data Studio to [periodically run 'git fetch']({0})?YesHEAD version of '{0}' is not available.TheirsYoursAdd to WorkspaceAdd a new remote...Add remote from URLAdd remote from {0}Add RemoteAlwaysThis will create a Git repository in '{0}'. Are you sure you want to continue?Failed to authenticate to git remote.Failed to authenticate to git remote:
{0}A branch named '{0}' already existsBranch nameThe new branch will be '{0}'Branch name needs to match regex: {0}Can't push refs to remote. Try running 'Pull' first to integrate your changes.Checkout detached...Choose Folder...Please clean your repository working tree before checkout.Clone from {0}Cloning git repository '{0}'...Commit Staged ChangesCreate Empty CommitCommit AnywayCommit HashCommit messageCommit to a New BranchMessage (commit on '{0}')You are trying to commit to a protected branch and you might not have permission to push your commits to the remote.
How would you like to proceed?Are you sure you want to DELETE {0}?
This is IRREVERSIBLE!
This file will be FOREVER LOST if you proceed.Are you sure you want to DELETE {0} files?
This is IRREVERSIBLE!
These files will be FOREVER LOST if you proceed.Are you sure you want to discard changes in {0}?Are you sure you want to discard ALL changes in {0} files?
This is IRREVERSIBLE!
Your current working set will be FOREVER LOST if you proceed.{0}
This is IRREVERSIBLE, your current working set will be FOREVER LOST.Are you sure you want to discard changes in {0}?Are you sure you want to discard changes in {0} files?Are you sure you want to create an empty commit?The branch '{0}' is not fully merged. Delete anyway?You are about to force push your changes, this can be destructive and could inadvertently overwrite changes made by others.
Are you sure to continue?You are about to commit your changes without verification, this skips pre-commit hooks and can be undesirable.
Are you sure to continue?The branch '{0}' has no remote branch. Would you like to publish this branch?Are you sure you want to restore {0}?Are you sure you want to restore {0} files?Are you sure you want to stage {0} with merge conflicts?Are you sure you want to stage {0} files with merge conflicts?Create new branch...Create new branch from...Initialize RepositoryCurrentDefaultDelete FileDelete BranchDelete fileDelete FilesFile '{0}' was deleted by them and modified by us.
What would you like to do?File '{0}' was deleted by us and modified by them.
What would you like to do?Discard ChangesDiscard All {0} FilesDiscard 1 FileAre you sure you want to drop ALL stashes? There are {0} stashes that will be subject to pruning, and MAY BE IMPOSSIBLE TO RECOVER.Are you sure you want to drop ALL stashes? There is 1 stash that will be subject to pruning, and MAY BE IMPOSSIBLE TO RECOVER.Commit operation was cancelled due to empty commit message.Force CheckoutForce push is not allowed, please enable it with the 'git.allowForcePush' setting.Git errorGit: {0}Open Comparison{0} ↔ {1}{0} ({1}) ↔ {0} ({2}){0} (Index){0} ({1}){0} (Working Tree)Pick workspace folder to initialize git repo inInitialize RepositoryInvalid branch nameKeep Our VersionKeep Their VersionLearn MoreYour local changes would be overwritten by checkout.The last commit was a merge commit. Are you sure you want to undo it?There are merge conflicts. Resolve them before committing.Make sure you configure your 'user.name' and 'user.email' in git.NeverOK, Don't Show AgainOK, Don't Ask AgainThere are no changes to commit.There are no changes to stash.Can't undo because HEAD doesn't point to any commit.No rebase in progress.Your repository has no remotes.This repository has no remotes configured to fetch from.Your repository has no remotes configured to publish to.Your repository has no remotes configured to pull from.Your repository has no remotes configured to push to.There are no staged changes to commit.
Would you like to stage all your changes and commit them directly?There are no stashes in the repository.This repository has no tags.Commits without verification are not allowed, please enable them with the 'git.allowNoVerifyCommit' setting.Please check out a branch to push to a remote.OKOpen Git LogOpen RepositoryOpenOpen in New WindowPick a branch to pull fromPick a provider to publish the branch '{0}' to:Pick a remote to publish the branch '{0}' to:Pick a remote to pull the branch fromPick a stash to applyPick a stash to dropPick a stash to popWould you like to open the cloned repository?Would you like to open the initialized repository?Would you like to open the cloned repository, or add it to the current workspace?Would you like to open the initialized repository, or add it to the current workspace?Please provide a new branch namePlease provide the commit hashPlease provide a commit messagePlease provide a remote nameOptionally provide a stash messagePlease provide a message to annotate the tagPlease provide a tag namePublish to {0}Remote '{0}' already exists.Remote branch at {0}Remote nameRemote name format invalidPick a remote to removeClone from URLRestore fileRestore filesSave All & CommitSave All & StashSelect a branch to merge fromSelect a branch to rebase ontoSelect a ref to checkoutSelect a ref to checkout in detached modeSelect a ref to create the '{0}' branch fromSelect a tag to deleteSelect a branch to deleteSelect log levelSelect Repository LocationShow Command OutputStash AnywayThere were merge conflicts while applying the stash.Stash messageStash & CheckoutAre you sure you want to drop the stash: {0}?This action will pull and push commits from and to '{0}/{1}'.Tag at {0}MessageTag nameThere are {0} untracked files which will be DELETED FROM DISK if discarded.The following untracked file will be DELETED FROM DISK if discarded: {0}.Undo merge commitThere are {0} unsaved files.
Would you like to save them before committing?The following file has unsaved changes which won't be included in the commit if you proceed: {0}.
Would you like to save it before committing?There are {0} unsaved files.
Would you like to save them before stashing?The following file has unsaved changes which won't be included in the stash if you proceed: {0}.
Would you like to save it before stashing?This will DELETE {0} untracked files!
This is IRREVERSIBLE!
These files will be FOREVER LOST.YesDiscard 1 Tracked FileDiscard {0} Tracked FilesYes, Don't Show AgainLog level: {0}Skipped found git in: {0}Using git {0} from {1}Validating found git in: {0}There are no available repositoriesAbsolute paths not supported in 'git.scanRepositories' setting.Choose a repositoryUnable to automatically open the git repository at '{0}'. To open that git repository, open it directly as a folder in VS Code.The '{0}' repository has {1} submodules which won't be opened automatically. You can still open each one individually by opening a file within.Would you like to add '{0}' to .gitignore?Conflict: Added By ThemConflict: Added By UsAlways PullConflict: Both AddedConflict: Both DeletedConflict: Both ModifiedChangesCommitIt's not possible to change the commit message in the middle of a rebase. Please complete the rebase operation and use interactive rebase instead.Message ({0} to commit){0} characters left in current line{0} characters over {1} in current lineCurrent commit message only contains whitespace charactersMessage ({0} to commit on '{1}')DeletedConflict: Deleted By ThemConflict: Deleted By UsDon't Pull{0} (Deleted){0} (Index){0} (Ours){0} (Theirs){0} (Untracked){0} (Working Tree)The git repository at '{0}' has too many active changes, only a subset of Git features will be enabled.IgnoredIndex AddedIndex CopiedIndex DeletedIndex ModifiedIndex RenamedIntent to AddMerge ChangesModifiedDon't Show AgainNoOKOpenOpen MergePullIt looks like the current branch '{0}' might have been rebased. Are you sure you still want to pull into it?It looks like the current branch might have been rebased. Are you sure you still want to pull into it?Pull {0} commits from {1}/{2}Pull {0} and push {1} commits between {2}/{3}Push {0} commits to {1}/{2}Successfully pushed.Staged ChangesSynchronize ChangesSyncing. Cancelling may cause serious damages to the repositoryToo many changes were detected. Only the first {0} changes will be shown below.UntrackedUntracked ChangesYesCheckout branch/tag...Publish BranchPublish to {0}Publish to...RebasingSynchronizing Changes...EmailOpen ComparisonGit HistoryStaged ChangesUncommitted ChangesYouColor for added resources.Color for resources with conflicts.Color for deleted resources.Color for ignored resources.Color for modified resources.Color for renamed or copied resources.Color for deleted resources which have been staged.Color for modified resources which have been staged.Color for submodule resources.Color for untracked resources.Add Remote...Get Remote SourcesGet RepositoriesGet Repository StateCreate Branch...Create Branch From...Checkout to...Checkout to (Detached)...Cherry Pick...Discard ChangesDiscard All ChangesDiscard All Tracked ChangesDiscard All Untracked ChangesCloneClone (Recursive)Close RepositoryClose All Diff EditorsCommitCommit AllCommit All (Amend)Commit All (Amend, No Verify)Commit All (No Verify)Commit All (Signed Off)Commit All (Signed Off, No Verify)Commit EmptyCommit Empty (No Verify)Accept Commit MessageDiscard Commit MessageCommit (No Verify)Commit StagedCommit Staged (Amend)Commit Staged (Amend, No Verify)Commit Staged (No Verify)Commit Staged (Signed Off)Commit Staged (Signed Off, No Verify)Create TagDelete Branch...Delete TagFetchFetch From All RemotesFetch (Prune)Accept MergeAdd to .gitignoreInitialize RepositoryMerge Branch...Open All ChangesOpen ChangesOpen FileOpen File (HEAD)Open RepositoryPublish Branch...PullPull from...Pull (Rebase)PushPush (Follow Tags)Push (Follow Tags, Force)Push (Force)Push TagsPush to...Push to... (Force)Rebase Branch...Abort RebaseRefreshRemove RemoteRenameRename Branch...Restore Commit TemplateOpen Containing FolderReveal in FinderReveal in File ExplorerReveal in Explorer ViewRevert ChangeRevert Selected RangesSet Log Level...Show Git OutputStage ChangesStage All ChangesStage All Merge ChangesStage All Tracked ChangesStage All Untracked ChangesStage ChangeStage Selected RangesStashApply Stash...Apply Latest StashDrop Stash...Drop All Stashes...Stash (Include Untracked)Pop Stash...Pop Latest StashSyncSync (Rebase)Compare with SelectedCopy Commit IDCopy Commit MessageOpen ChangesSelect for CompareUndo Last CommitUnstage ChangesUnstage All ChangesUnstage Selected RangesControls whether force push (with or without lease) is enabled.Controls whether commits without running pre-commit and commit-msg hooks are allowed.Always show the Staged Changes resource group.Controls the signoff flag for all commits.Configures when repositories should be automatically detected.Disable automatic repository scanning.Scan for parent folders of open files.Scan for subfolders of the currently opened folder.Scan for both subfolders of the current opened folder and parent folders of open files.Stash any changes before pulling and restore them after successful pull.When set to true, commits will automatically be fetched from the default remote of the current Git repository. Setting to `all` will fetch from all remotes.Duration in seconds between each automatic git fetch, when `#git.autofetch#` is enabled.Whether auto refreshing is enabled.Prefix used when creating a new branch.List of protected branches. By default, a prompt is shown before changes are committed to a protected branch. The prompt can be controlled using the `#git.branchProtectionPrompt#` setting.Controls whether a prompt is being before changes are committed to a protected branch.Always commit changes to the protected branch.Always commit changes to a new branch.Always prompt before changes are committed to a protected branch.List of dictionaries used for the randomly generated branch name. Each value represents the dictionary used to generate the segment of the branch name. Supported dictionaries: `adjectives`, `animals`, `colors` and `numbers`.A random adjectiveA random animal nameA random color nameA random number between 100 and 999Controls whether a random name is generated when creating a new branch.Controls the sort order for branches.A regular expression to validate new branch names.The character to replace whitespace in new branch names, and to separate segments of a randomly generated branch name.Controls what type of git refs are listed when running `Checkout to...`.Local branchesRemote branchesTagsControls whether the diff editor should be automatically closed when changes are stashed, committed, discarded, staged, or unstaged.List of git commands (ex: commit, push) that would have their `stdout` logged to the [git output](command:git.showOutput). If the git command has a client-side hook configured, the client-side hook's `stdout` will also be logged to the [git output](command:git.showOutput).{Locked='](command:git.showOutput'}
Do not translate the 'command:*' part inside of the '(..)'. It is an internal command syntax for Azure Data Studio
Please make sure there is no space between the right bracket and left parenthesis: ]( this is an internal syntax for linksAlways confirm the creation of empty commits for the 'Git: Commit Empty' command.Controls whether to ask for confirmation before force-pushing.Controls whether to ask for confirmation before committing without verification.Confirm before synchronizing git repositories.Controls the Git count badge.Count all changes.Turn off counter.Count only tracked changes.Controls whether Git contributes colors and badges to the Explorer and the Open Editors view.The default location to clone a git repository.Controls whether to automatically detect git submodules.Controls the limit of git submodules detected.Controls what changes are discarded by the `Discard all changes` command. `all` discards all changes. `tracked` discards only tracked files. `prompt` shows a prompt dialog every time the action is run.Enables commit signing with GPG or X.509.Commit all changes when there are no staged changes.Controls whether the Git Sync command appears in the status bar.Whether git is enabled.Experimental improvements for the git setup flow.When enabled, fetch all branches when pulling. Otherwise, fetch just the current one.Follow push all tags when running the sync command.Ignores the legacy Git warning.Ignores the warning when there are too many changes in a repository.Ignores the warning when Git is missing.Ignores the warning when it looks like the branch might have been rebased when pulling.Ignore modifications to submodules in the file tree.Ignores the warning when Git 2.25 - 2.26 is installed on Windows.List of git repositories to ignore.Controls when to show commit message input validation.Controls the commit message length threshold for showing a warning.Controls the commit message subject length threshold for showing a warning. Unset it to inherit the value of `config.inputValidationLength`.Specifies how much information (if any) to log to the [git output](command:git.showOutput).{Locked='](command:git.showOutput'}
Do not translate the 'command:*' part inside of the '(..)'. It is an internal command syntax for VS Code
Please make sure there is no space between the right bracket and left parenthesis: ]( this is an internal syntax for linksLog only critical informationLog only debug, information, warning, error, and critical informationLog only error, and critical informationLog only information, warning, error, and critical informationLog nothingLog all informationLog only warning, error, and critical informationOpen the merge editor for files that are currently under conflict.Controls whether to open a repository automatically after cloning.Always open in current window.Always open in a new window.Always prompt for action.Only open in current window when no folder is opened.Controls whether the diff editor should be opened when clicking a change. Otherwise the regular editor will be opened.Path and filename of the git executable, e.g. `C:\Program Files\Git\bin\git.exe` (Windows). This can also be an array of string values containing multiple paths to look up.Runs a git command after a successful commit.Don't run any command after a commit.Run 'Git Push' after a successful commit.Run 'Git Sync' after a successful commit.Controls whether Git should check for unsaved files before committing.Check for any unsaved files.Disable this check.Check only for unsaved staged files.Controls whether Git should check for unsaved files before stashing changes.Check for any unsaved files.Disable this check.Check only for unsaved staged files.Prune when fetching.Fetch all tags when pulling.Force git to use rebase when running the sync command.List of folders that are ignored while scanning for Git repositories when `#git.autoRepositoryDetection#` is set to `true` or `subFolders`.Controls the depth used when scanning workspace folders for Git repositories when `#git.autoRepositoryDetection#` is set to `true` or `subFolders`. Can be set to `-1` for no limit.Controls whether to require explicit Git user configuration or allow Git to guess if missing.List of paths to search for git repositories in.Controls whether an action button is shown in the Source Control view.Show an action button to commit changes when the local branch has modified files ready to be committed.Show an action button to publish the local branch when it does not have a tracking remote branch.Show an action button to synchronize changes when the local branch is either ahead or behind the remote branch.Controls whether to show the commit input in the Git source control panel.Controls whether to show an inline Open File action in the Git changes view.Controls whether git actions should show progress.Controls whether to show a notification when a push is successful.Control which changes are automatically staged by Smart Commit.Automatically stage all changes.Automatically stage tracked changes only.Controls how to limit the number of changes that can be parsed from Git status command. Can be set to 0 for no limit.Suggests to enable smart commit (commit all changes when there are no staged changes).Controls whether a notification comes up when running the Sync action, which allows the user to cancel the operation.Controls whether to enable VS Code to be the authentication handler for git processes spawned in the integrated terminal. Note: terminals need to be restarted to pick up a change in this setting.Controls whether to enable VS Code to be git editor for git processes spawned in the integrated terminal. Note: terminals need to be restarted to pick up a change in this setting.Controls which date to use for items in the Timeline view.Use the authored dateUse the committed dateControls whether to show the commit author in the Timeline view.Controls whether to show uncommitted changes in the Timeline view.Controls how untracked changes behave.Untracked changes are hidden and excluded from several actions.All changes, tracked and untracked, appear together and behave equally.Untracked changes appear separately in the Source Control view. They are also excluded from several actions.Controls whether to use the message from the commit input box as the default stash message.Controls whether a full text editor will be used to author commit messages, whenever no message is provided in the commit input box.Controls whether force pushing uses the safer force-with-lease variant.Controls whether GIT_ASKPASS should be overwritten to use the integrated version.Enable verbose output when `#git.useEditorAsCommitInput#` is enabled.Git SCM IntegrationGitBranchChangesCommitAmendSign OffGitPull, PushRemoteStashTagsYou can clone a repository locally.
[Clone Repository](command:git.clone 'Clone a repository once the git extension has activated'){Locked='](command:git.clone'}
Do not translate the 'command:*' part inside of the '(..)'. It is an internal command syntax for Azure Data Studio
Please make sure there is no space between the right bracket and left parenthesis: ]( this is an internal syntax for linksTo learn more about how to use git and source control in Azure Data Studio [read our docs](https://aka.ms/vscode-scm).If you would like to use git features, please enable git in your [settings](command:workbench.action.openSettings?%5B%22git.enabled%22%5D).
To learn more about how to use git and source control in VS Code [read our docs](https://aka.ms/vscode-scm).{Locked='](command:workbench.action.openSettings?%5B%22git.enabled%22%5D'}
Do not translate the 'command:*' part inside of the '(..)'. It is an internal command syntax for Azure Data Studio
Please make sure there is no space between the right bracket and left parenthesis: ]( this is an internal syntax for linksIn order to use git features, you can open a folder containing a git repository or clone from a URL.
[Open Folder](command:vscode.openFolder)
[Clone Repository](command:git.clone)
To learn more about how to use git and source control in Azure Data Studio [read our docs](https://aka.ms/vscode-scm).{Locked='](command:vscode.openFolder'}
Do not translate the 'command:*' part inside of the '(..)'. It is an internal command syntax for Azure Data Studio
Please make sure there is no space between the right bracket and left parenthesis: ]( this is an internal syntax for linksThe workspace currently open doesn't have any folders containing git repositories.
[Add Folder to Workspace](command:workbench.action.addRootFolder)
To learn more about how to use git and source control in Azure Data Studio [read our docs](https://aka.ms/vscode-scm).{Locked='](command:workbench.action.addRootFolder'}
Do not translate the 'command:*' part inside of the '(..)'. It is an internal command syntax for Azure Data Studio
Please make sure there is no space between the right bracket and left parenthesis: ]( this is an internal syntax for linksThe folder currently open doesn't have a git repository. You can initialize a repository which will enable source control features powered by git.
[Initialize Repository](command:git.init?%5Btrue%5D)
To learn more about how to use git and source control in Azure Data Studio [read our docs](https://aka.ms/vscode-scm).{Locked='](command:git.init?%5Btrue%5D'}
Do not translate the 'command:*' part inside of the '(..)'. It is an internal command syntax for Azure Data Studio
Please make sure there is no space between the right bracket and left parenthesis: ]( this is an internal syntax for linksInstall Git, a popular source control system, to track code changes and collaborate with others. Learn more in our [Git guides](https://aka.ms/vscode-scm).Source control depends on Git being installed.
[Download Git for Linux](https://git-scm.com/download/linux)
After installing, please [reload](command:workbench.action.reloadWindow) (or [troubleshoot](command:git.showOutput)). Additional source control providers can be installed [from the Marketplace](command:workbench.extensions.search?%22%40category%3A%5C%22scm%20providers%5C%22%22).{Locked='](command:workbench.action.reloadWindow'}
Do not translate the 'command:*' part inside of the '(..)'. It is an internal command syntax for Azure Data Studio
Please make sure there is no space between the right bracket and left parenthesis: ]( this is an internal syntax for links[Download Git for macOS](https://git-scm.com/download/mac)
After installing, please [reload](command:workbench.action.reloadWindow) (or [troubleshoot](command:git.showOutput)). Additional source control providers can be installed [from the Marketplace](command:workbench.extensions.search?%22%40category%3A%5C%22scm%20providers%5C%22%22).{Locked='](command:workbench.action.reloadWindow'}
Do not translate the 'command:*' part inside of the '(..)'. It is an internal command syntax for Azure Data Studio
Please make sure there is no space between the right bracket and left parenthesis: ]( this is an internal syntax for links[Download Git for Windows](https://git-scm.com/download/win)
After installing, please [reload](command:workbench.action.reloadWindow) (or [troubleshoot](command:git.showOutput)). Additional source control providers can be installed [from the Marketplace](command:workbench.extensions.search?%22%40category%3A%5C%22scm%20providers%5C%22%22).{Locked='](command:workbench.action.reloadWindow'}
Do not translate the 'command:*' part inside of the '(..)'. It is an internal command syntax for Azure Data Studio
Please make sure there is no space between the right bracket and left parenthesis: ]( this is an internal syntax for linksThe workspace currently open doesn't have any folders containing git repositories. You can initialize a repository on a folder which will enable source control features powered by git.
[Initialize Repository](command:git.init)
To learn more about how to use git and source control in Azure Data Studio [read our docs](https://aka.ms/vscode-scm).{Locked='](command:git.init'}
Do not translate the 'command:*' part inside of the '(..)'. It is an internal command syntax for Azure Data Studio
Please make sure there is no space between the right bracket and left parenthesis: ]( this is an internal syntax for links