Missing or invalid credentials. No Ask Me Later Would you like Azure Data Studio to [periodically run 'git fetch']({0})? Yes HEAD version of '{0}' is not available. Add to Workspace Add a new remote... Add remote from URL Add remote from {0} Add Remote Always This 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 exists Branch name Branch name needs to match regex: {0} Can't push refs to remote. Try running 'Pull' first to integrate your changes. Log level changed to: {0} Checkout detached... Choose Folder... Please clean your repository working tree before checkout. Clone from {0} Cloning git repository '{0}'... Commit Staged Changes Create Empty Commit Commit Hash Commit message Message (commit on '{0}') 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 upstream 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 Repository Current Delete File Delete Branch Delete file Delete Files File '{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 Changes Discard All {0} Files Discard 1 File Force Checkout Force push is not allowed, please enable it with the 'git.allowForcePush' setting. Git error Git: {0} {0} ⟷ {1} {0} ({1}) ⟷ {0} ({2}) {0} (Index) {0} ({1}) {0} (Working Tree) Pick workspace folder to initialize git repo in Initialize Repository Invalid branch name Keep Our Version Keep Their Version Learn More Your 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. Never OK, Don't Show Again OK, Don't Ask Again There 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. OK Open Git Log Open Repository Open Open in New Window 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 stash to apply Pick a stash to drop Pick a stash to pop Would 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 name Please provide the commit hash Please provide a commit message Please provide a remote name Optionally provide a stash message Please provide a message to annotate the tag Please provide a tag name Publish to {0} Remote '{0}' already exists. Remote branch at {0} Remote name Remote name format invalid Pick a remote to remove Clone from URL Restore file Restore files Save All & Commit Save All & Stash Select a branch to merge from Select a branch to rebase onto Select a ref to checkout Select a ref to checkout in detached mode Select a ref to create the '{0}' branch from Select a tag to delete Select a branch to delete Select log level Select Repository Location Show Command Output Stash Anyway There were merge conflicts while applying the stash. Stash message Stash & Checkout Are you sure you want to drop the stash: {0}? This action will push and pull commits to and from '{0}/{1}'. Tag at {0} Message Tag name There 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 commit There 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. Yes Discard 1 Tracked File Discard {0} Tracked Files Yes, Don't Show Again Skipped found git in: {0} Using git {0} from {1} Validating found git in: {0} There are no available repositories Absolute paths not supported in 'git.scanRepositories' setting. Choose a repository The '{0}' repository has {1} submodules which won't be opened automatically. You can still open each one individually by opening a file within. Branch name $(error) Error: {0} No remote repositories found. Choose a URL to clone from. Provide repository URL Provide repository URL or pick a repository source. Repository name Repository name (type to search) URL Would you like to add '{0}' to .gitignore? Conflict: Added By Them Conflict: Added By Us Always Pull Conflict: Both Added Conflict: Both Deleted Conflict: Both Modified Changes Commit 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. Message ({0} to commit) {0} characters left in current line {0} characters over {1} in current line Current commit message only contains whitespace characters Message ({0} to commit on '{1}') Deleted Conflict: Deleted By Them Conflict: Deleted By Us Don'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. Ignored Index Added Index Copied Index Deleted Index Modified Index Renamed Intent to Add Merge Changes Modified Don't Show Again Open Pull 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? Pull {0} commits from {1}/{2} Pull {0} and push {1} commits between {2}/{3} Push {0} commits to {1}/{2} Successfully pushed. Staged Changes Synchronize Changes Syncing. Cancelling may cause serious damages to the repository Untracked Untracked Changes Yes Checkout branch/tag... Publish Changes Publish to {0} Publish to... Rebasing Synchronizing Changes... Index {0} — {1} {2} {3} Git History Staged Changes Uncommitted Changes You Working Tree Color 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... Create Branch... Create Branch From... Checkout to... Checkout to (Detached)... Cherry Pick... Discard Changes Discard All Changes Discard All Tracked Changes Discard All Untracked Changes Clone Clone (Recursive) Close Repository Commit 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 (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) Create Tag Delete Branch... Delete Tag Fetch Fetch From All Remotes Fetch (Prune) Add to .gitignore Initialize Repository Merge Branch... Open All Changes Open Changes Open File Open File (HEAD) Open Repository Publish Branch... Pull Pull from... Pull (Rebase) Push Push (Follow Tags) Push (Follow Tags, Force) Push (Force) Push Tags Push to... Push to... (Force) Rebase Branch... Abort Rebase Refresh Remove Remote Rename Rename Branch... Restore Commit Template Reveal in Side Bar Revert Change Revert Selected Ranges Set Log Level... Show Git Output Stage Changes Stage All Changes Stage All Merge Changes Stage All Tracked Changes Stage All Untracked Changes Stage Change Stage Selected Ranges Stash Apply Stash... Apply Latest Stash Drop Stash... Stash (Include Untracked) Pop Stash... Pop Latest Stash Sync Sync (Rebase) Compare with Selected Copy Commit ID Copy Commit Message Open Changes Select for Compare Undo Last Commit Unstage Changes Unstage All Changes Unstage Selected Ranges Controls 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. Controls the sort order for branches. A regular expression to validate new branch names. The character to replace whitespace in new branch names. Controls what type of git refs are listed when running `Checkout to...`. Local branches Remote branches Tags Always 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. 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`. 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. 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 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. 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 Azure Data Studio 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 which date to use for items in the Timeline view. Use the authored date Use the committed date Controls whether to show the commit author 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 force pushing uses the safer force-with-lease variant. Git SCM Integration Git Branch Changes Commit Amend Sign Off Git Pull, Push Remote Stash Tags You can clone a repository locally. [Clone Repository](command:git.clone 'Clone a repository once the git extension has activated') To 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 Azure Data Studio [read our docs](https://aka.ms/vscode-scm). 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). The 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). The 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). A valid git installation was not detected, more details can be found in the [git output](command:git.showOutput). Please [install git](https://git-scm.com/), or learn more about how to use git and source control in Azure Data Studio in [our docs](https://aka.ms/vscode-scm). If you're using a different version control system, you can [search the Marketplace](command:workbench.extensions.search?%22%40category%3A%5C%22scm%20providers%5C%22%22) for additional extensions. The 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).