$(info) Remote "{0}" has no tags.

$(info) This repository has no tags.

"{0}" has fingerprint "{1}"

A branch named "{0}" already exists

A git repository was found in the parent folders of the workspace or the open file(s). Would you like to open the repository?

Absolute paths not supported in "git.scanRepositories" setting.

Add Remote

Add a new remote...

Add remote from URL

Add remote from {0}

Add to Workspace

All Repositories

Always

Always Pull

Are you sure you want to DELETE {0} files?\nThis is IRREVERSIBLE!\nThese files will be FOREVER LOST if you proceed.

Are you sure you want to DELETE {0}?\nThis is IRREVERSIBLE!\nThis file will be FOREVER LOST if you proceed.

Are you sure you want to continue connecting?

Are you sure you want to create an empty commit?

Are you sure you want to discard ALL changes in {0} files?\nThis is IRREVERSIBLE!\nYour current working set will be FOREVER LOST if you proceed.

Are you sure you want to discard changes in {0} files?

Are you sure you want to discard changes in {0}?

Are 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.

Are you sure you want to drop the stash: {0}?

Are you sure you want to restore {0} files?

Are you sure you want to restore {0}?

Are you sure you want to stage {0} files with merge conflicts?

Are you sure you want to stage {0} with merge conflicts?

Ask Me Later

Branch name

Branch name needs to match regex: {0}

Can\'t push refs to remote. Try running "Pull" first to integrate your changes.

Can\'t undo because HEAD doesn\'t point to any commit.

Changes

Checking Out Branch/Tag...

Checking Out Changes...

Checkout Branch/Tag...

Checkout detached...

Choose Folder...

Choose a folder to clone {0} into

Choose a repository

Choose which repository to clone

Clone from URL

Clone from {0}

Cloning git repository "{0}"...

Commit

Commit & Push Changes

Commit & Sync Changes

Commit Anyway

Commit Changes

Commit Changes on "{0}"

Commit Changes to New Branch

Commit Hash

Commit Staged Changes

Commit message

Commit operation was cancelled due to empty commit message.

Commit to New Branch & Push Changes

Commit to New Branch & Synchronize Changes

Commit to a New Branch

Commits without verification are not allowed, please enable them with the "git.allowNoVerifyCommit" setting.

Committing & Pushing Changes...

Committing & Synchronizing Changes...

Committing Changes to New Branch...

Committing Changes...

Committing to New Branch & Pushing Changes...

Committing to New Branch & Synchronizing Changes...

Conflict: Added By Them

Conflict: Added By Us

Conflict: Both Added

Conflict: Both Deleted

Conflict: Both Modified

Conflict: Deleted By Them

Conflict: Deleted By Us

Continue Rebase

Continuing Rebase...

Could not clone your repository as Git is not installed.

Create Empty Commit

Create new branch from...

Create new branch...

Current

Current commit message only contains whitespace characters

Delete Branch

Delete File

Delete Files

Delete file

Deleted

Discard 1 File

Discard 1 Tracked File

Discard All {0} Files

Discard Changes

Discard {0} Tracked Files

Don\'t Pull

Don\'t Show Again

Download Git

Failed to authenticate to git remote.

Failed to authenticate to git remote:\n\n{0}

File "{0}" was deleted by them and modified by us.\n\nWhat would you like to do?

File "{0}" was deleted by us and modified by them.\n\nWhat would you like to do?

Force Checkout

Force push is not allowed, please enable it with the "git.allowForcePush" setting.

Git History

Git error

Git local working changes

Git repositories were found in the parent folders of the workspace or the open file(s). Would you like to open the repositories?

Git: {0}

HEAD version of "{0}" is not available.

Ignored

Incoming

Index Added

Index Copied

Index Deleted

Index Modified

Index Renamed

Initialize Repository

Intent to Add

Intent to Rename

Invalid branch name

It 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?

It\'s not possible to change the commit message in the middle of a rebase. Please complete the rebase operation and use interactive rebase instead.

Keep Our Version

Keep Their Version

Learn More

Log level: {0}

Make sure you configure your "user.name" and "user.email" in git.

Manage Unsafe Repositories

Merge Changes

Message

Message (commit on "{0}")

Message ({0} to commit on "{1}")

Message ({0} to commit)

Migrate Changes

Modified

Never

No rebase in progress.

OK, Don\'t Ask Again

OK, Don\'t Show Again

Open

Open Comparison

Open Git Log

Open Merge

Open Repositories In Parent Folders

Open Repository

Open in New Window

Optionally provide a stash message

Passphrase

Pick a branch to pull from

Pick a provider to publish the branch "{0}" to:

Pick a remote to publish the branch "{0}" to:

Pick a remote to pull the branch from

Pick a remote to remove

Pick a repository to mark as safe and open

Pick a repository to open

Pick a stash to apply

Pick a stash to drop

Pick a stash to pop

Pick workspace folder to initialize git repo in

Please check out a branch to push to a remote.

Please clean your repository working tree before checkout.

Please provide a commit message

Please provide a message to annotate the tag

Please provide a new branch name

Please provide a remote name

Please provide a tag name

Please provide the commit hash

Publish Branch

Publish Branch {Locked="Branch"} Do not translate "Branch" as it is a git term

Publish Branch "{0}" {Locked="Branch"} Do not translate "Branch" as it is a git term

Publish to {0}

Publish to...

Publishing Branch "{0}"... {Locked="Branch"} Do not translate "Branch" as it is a git term

Publishing Branch... {Locked="Branch"} Do not translate "Branch" as it is a git term

Pull

Pull {0} and push {1} commits between {2}/{3}

Pull {0} commits from {1}/{2}

Push {0} commits to {1}/{2}

Rebasing

Remote "{0}" already exists.

Remote branch at {0}

Remote name

Remote name format invalid

Replace Local Tag(s)

Restore file

Restore files

Save All & Commit

Save All & Stash

Select a branch or tag to checkout

Select a branch to checkout in detached mode

Select a branch to delete

Select a branch to merge from

Select a branch to rebase onto

Select a ref to create the branch from

Select a remote to delete a tag from

Select a remote to fetch

Select a tag to delete

Select as Repository Destination

Show Changes

Show Command Output

Skipped found git in: "{0}"

Staged Changes

Stash & Checkout

Stash Anyway

Stash message

Stashed Changes

Successfully pushed.

Synchronize Changes

Synchronizing Changes...

Syncing. Cancelling may cause serious damages to the repository

Tag at {0}

Tag name

The "{0}" repository has {1} submodules which won\'t be opened automatically. You can still open each one individually by opening a file within.

The branch "{0}" has no remote branch. Would you like to publish this branch?

The branch "{0}" is not fully merged. Delete anyway?

The current branch is not published to the remote. Would you like to publish it to access your changes elsewhere?

The following file has unsaved changes which won\'t be included in the commit if you proceed: {0}.\n\nWould you like to save it before committing?

The following file has unsaved changes which won\'t be included in the stash if you proceed: {0}.\n\nWould you like to save it before stashing?

The following untracked file will be DELETED FROM DISK if discarded: {0}.

The git repositories in the current folder are potentially unsafe as the folders are owned by someone other than the current user.

The git repository at "{0}" has too many active changes, only a subset of Git features will be enabled.

The git repository in the current folder is potentially unsafe as the folder is owned by someone other than the current user.

The last commit was a merge commit. Are you sure you want to undo it?

The new branch will be "{0}"

The repository does not have any commits. Please make an initial commit before creating a stash.

The selection range does not contain any changes.

There are merge conflicts. Resolve them before committing.

There are no available repositories

There are no changes to commit.

There are no changes to stash.

There are no staged changes to commit.\n\nWould you like to stage all your changes and commit them directly?

There are no staged changes to stash.

There are no stashes in the repository.

There are {0} unsaved files.\n\nWould you like to save them before committing?

There are {0} unsaved files.\n\nWould you like to save them before stashing?

There are {0} untracked files which will be DELETED FROM DISK if discarded.

There were merge conflicts while applying the stash.

This action will pull and push commits from and to "{0}/{1}".

This repository has no remotes configured to fetch from.

This will DELETE {0} untracked files!\nThis is IRREVERSIBLE!\nThese files will be FOREVER LOST.

This will create a Git repository in "{0}". Are you sure you want to continue?

Too many changes were detected. Only the first {0} changes will be shown below.

Unable to pull from remote repository due to conflicting tag(s): {0}. Would you like to resolve the conflict by replacing the local tag(s)?

Uncommitted Changes

Undo merge commit

Untracked

Untracked Changes

Using git "{0}" from "{1}"

Validating found git in: "{0}"

Would you like to add "{0}" to .gitignore?

Would you like to open the cloned repository, or add it to the current workspace?

Would you like to open the cloned repository?

Would you like to open the initialized repository, or add it to the current workspace?

Would you like to open the initialized repository?

Would you like {0} to [periodically run "git fetch"]({1})?

Yes

Yes, Don\'t Show Again

You

You are about to commit your changes without verification, this skips pre-commit hooks and can be undesirable.\n\nAre you sure to continue?

You are about to force push your changes, this can be destructive and could inadvertently overwrite changes made by others.\n\nAre you sure to continue?

You are trying to commit to a protected branch and you might not have permission to push your commits to the remote.\n\nHow would you like to proceed?

Your local changes would be overwritten by checkout.

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.

Your repository has no remotes.

yes

{0} (Deleted)

{0} (Index)

{0} (Intent to add)

{0} (Ours)

{0} (Theirs)

{0} (Untracked)

{0} (Working Tree)

{0} ({1})

{0} ({1}) ↔ {0} ({2})

{0} Commit

{0} Commit & Push

{0} Commit & Sync

{0} Continue

{0} Fetch all remotes

{0} Publish Branch {Locked="Branch"} Do not translate "Branch" as it is a git term

{0} Sync Changes{1}{2}

{0} characters left in current line

{0} characters over {1} in current line

{0} ↔ {1}

{0}\n\nThis is IRREVERSIBLE, your current working set will be FOREVER LOST.

A git repository was found in the parent folders of the workspace or the open file(s). [Open Repository](command:git.openRepositoriesInParentFolders) Use the [git.openRepositoryInParentFolders](command:workbench.action.openSettings?%5B%22git.openRepositoryInParentFolders%22%5D) setting to control whether git repositories in parent folders of workspaces or open files are opened. To learn more [read our docs](https://aka.ms/vscode-git-repository-in-parent-folders). {Locked='](command:git.openRepositoriesInParentFolders'} {Locked='](command:workbench.action.openSettings?%5B%22git.openRepositoryInParentFolders%22%5D'} 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 links

A random adjective

A random animal name

A random color name

A random number between 100 and 999

A regular expression to validate new branch names.

Abort Merge

Abort Rebase

Accept Commit Message

Add Remote...

Add to .gitignore

All changes, tracked and untracked, appear together and behave equally.

Always commit changes to a new branch.

Always commit changes to the protected branch.

Always confirm the creation of empty commits for the 'Git: Commit Empty' command.

Always open a repository in parent folders of workspaces or open files.

Always open in a new window.

Always open in current window.

Always prompt before changes are committed to a protected branch.

Always prompt for action.

Always publish unpublished git state when using Continue Working On from a git repository

Always show the Staged Changes resource group.

Amend

Apply Latest Stash

Apply Stash...

Automatically stage all changes.

Automatically stage tracked changes only.

Branch

Changes

Check for any unsaved files.

Check only for unsaved staged files.

Checkout to (Detached)...

Checkout to...

Cherry Pick...

Clone

Clone (Recursive)

Clone Repository Locally and Open on Desktop...

Close All Diff Editors

Close Repository

Color for added resources.

Color for deleted resources which have been staged.

Color for deleted resources.

Color for ignored resources.

Color for modified resources which have been staged.

Color for modified resources.

Color for renamed or copied resources.

Color for resources with conflicts.

Color for submodule resources.

Color for untracked resources.

Commit

Commit (No Verify)

Commit All

Commit All (Amend)

Commit All (Amend, No Verify)

Commit All (No Verify)

Commit All (Signed Off)

Commit All (Signed Off, No Verify)

Commit Empty

Commit Empty (No Verify)

Commit Staged

Commit Staged (Amend)

Commit Staged (Amend, No Verify)

Commit Staged (No Verify)

Commit Staged (Signed Off)

Commit Staged (Signed Off, No Verify)

Commit all changes when there are no staged changes.

Compare with Selected

Complete Merge

Compute Conflicts With Git

Compute Conflicts With Git (Diff3)

Configures when repositories should be automatically detected.

Confirm before synchronizing git repositories.

Continue Working in New Local Clone

Control whether a repository in parent folders of workspaces or open files should be opened.

Control which changes are automatically staged by Smart Commit.

Controls how to limit the number of changes that can be parsed from Git status command. Can be set to 0 for no limit.

Controls how untracked changes behave.

Controls the Git count badge.

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`.

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 the limit of git submodules detected.

Controls the signoff flag for all commits.

Controls the sort order for branches.

Controls the threshold of the similarity index (i.e. amount of additions/deletions compared to the file's size) for changes in a pair of added/deleted files to be considered a rename.

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.

Controls what type of git refs are listed when running `Checkout to...`.

Controls when to show commit message input validation.

Controls whether GIT_ASKPASS should be overwritten to use the integrated version.

Controls whether Git contributes colors and badges to the Explorer and the Open Editors view.

Controls whether Git should check for unsaved files before committing.

Controls whether Git should check for unsaved files before stashing changes.

Controls whether a branch that does not have outgoing commits is fast-forwarded before it is checked out.

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 a notification comes up when running the Sync action, which allows the user to cancel the operation.

Controls whether a prompt is being shown before changes are committed to a protected branch.

Controls whether a random name is generated when creating a new branch.

Controls whether an action button is shown in the Source Control view.

Controls whether commits without running pre-commit and commit-msg hooks are allowed.

Controls whether force push (with or without lease) is enabled.

Controls whether force pushing uses the safer force-with-lease variant.

Controls whether git actions should show progress.

Controls whether the Git Sync command appears in the status bar.

Controls whether the diff editor should be automatically closed when changes are stashed, committed, discarded, staged, or unstaged.

Controls whether the diff editor should be opened when clicking a change. Otherwise the regular editor will be opened.

Controls whether to ask for confirmation before committing without verification.

Controls whether to ask for confirmation before force-pushing.

Controls whether to automatically detect git submodules.

Controls whether to enable VS Code to be the 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 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 open a repository automatically after cloning.

Controls whether to optimistically update the state of the Source Control view after running git commands.

Controls whether to publish unpublished git state when using Continue Working On from a git repository.

Controls whether to require explicit Git user configuration or allow Git to guess if missing.

Controls whether to show a notification when a push is successful.

Controls whether to show an inline Open File action in the Git changes view.

Controls whether to show the commit author in the Timeline view.

Controls whether to show the commit input in the Git source control panel.

Controls whether to show uncommitted changes in the Timeline view.

Controls whether to use the message from the commit input box as the default stash message.

Controls which date to use for items in the Timeline view.

Copy Commit ID

Copy Commit Message

Count all changes.

Count only tracked changes.

Create Branch From...

Create Branch...

Create Tag

Delete Branch...

Delete Remote Tag

Delete Tag

Disable automatic repository scanning.

Disable this check.

Discard All Changes

Discard All Tracked Changes

Discard All Untracked Changes

Discard Changes

Discard Commit Message

Don't run any command after a commit.

Drop All Stashes...

Drop Stash...

Duration in seconds between each automatic git fetch, when `#git.autofetch#` is enabled.

Enable verbose output when `#git.useEditorAsCommitInput#` is enabled.

Enables commit signing with GPG or X.509.

Experimental improvements for the git setup flow.

Fetch

Fetch (Prune)

Fetch From All Remotes

Fetch all tags when pulling.

Force git to use rebase when running the sync command.

Get Remote Sources

Get Repositories

Get Repository State

Git

Git SCM Integration

Git repositories were found in the parent folders of the workspace or the open file(s). [Open Repository](command:git.openRepositoriesInParentFolders) Use the [git.openRepositoryInParentFolders](command:workbench.action.openSettings?%5B%22git.openRepositoryInParentFolders%22%5D) setting to control whether git repositories in parent folders of workspace or open files are opened. To learn more [read our docs](https://aka.ms/vscode-git-repository-in-parent-folders). {Locked='](command:git.openRepositoriesInParentFolders'} {Locked='](command:workbench.action.openSettings?%5B%22git.openRepositoryInParentFolders%22%5D'} 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 links

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 links

Ignore modifications to submodules in the file tree.

Ignores the legacy Git warning.

Ignores the warning when Git 2.25 - 2.26 is installed on Windows.

Ignores the warning when Git is missing.

Ignores the warning when it looks like the branch might have been rebased when pulling.

Ignores the warning when there are too many changes in a repository.

In 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 links

Initialize Repository

Install 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).

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`.

List of folders that are ignored while scanning for Git repositories when `#git.autoRepositoryDetection#` is set to `true` or `subFolders`.

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 links

List of git repositories to ignore.

List of paths to search for git repositories in.

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.

Local branches

Manage Unsafe Repositories

Merge Branch...

Never open a repository in parent folders of workspaces or open files.

Never publish unpublished git state when using Continue Working On from a git repository

Only open in current window when no folder is opened.

Open All Changes

Open Changes

Open Containing Folder

Open File

Open File (HEAD)

Open Repositories In Parent Folders

Open Repository

Open the merge editor for files that are currently under conflict.

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.

Pop Latest Stash

Pop Stash...

Prefix used when creating a new branch.

Prompt before opening a repository the parent folders of workspaces or open files.

Prompt to publish unpublished git state when using Continue Working On from a git repository

Prune when fetching.

Publish Branch...

Pull

Pull (Rebase)

Pull from...

Pull, Push

Push

Push (Follow Tags)

Push (Follow Tags, Force)

Push (Force)

Push Tags

Push all annotated tags when running the sync command.

Push to...

Push to... (Force)

Rebase Branch...

Refresh

Remember the last git command that ran after a commit.

Remote

Remote branches

Remove Remote

Rename

Rename Branch...

Resolve in Merge Editor

Restore Commit Template

Reveal in Explorer View

Reveal in File Explorer

Reveal in Finder

Revert Change

Revert Selected Ranges

Run 'git pull' and 'git push' after a successful commit.

Run 'git push' after a successful commit.

Run a git command after a successful commit.

Scan for both subfolders of the current opened folder and parent folders of open files.

Scan for parent folders of open files.

Scan for subfolders of the currently opened folder.

Scanning folder for git repositories...

Scanning workspace for git repositories...

Select for Compare

Show Git Output

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.

Sign Off

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

Stage All Changes

Stage All Merge Changes

Stage All Tracked Changes

Stage All Untracked Changes

Stage Change

Stage Changes

Stage Selected Ranges

Stash

Stash (Include Untracked)

Stash Staged

Stash any changes before pulling and restore them after successful pull.

Suggests to enable smart commit (commit all changes when there are no staged changes).

Sync

Sync (Rebase)