{"action":"opened","issue":{"url":"https://api.github.com/repos/git-for-windows/git/issues/609","labels_url":"https://api.github.com/repos/git-for-windows/git/issues/609/labels{/name}","comments_url":"https://api.github.com/repos/git-for-windows/git/issues/609/comments","events_url":"https://api.github.com/repos/git-for-windows/git/issues/609/events","html_url":"https://github.com/git-for-windows/git/issues/609","id":126918179,"number":609,"title":"git for windows 2.7.0 bash CLI pauses for input then prints \"it's a number\" or \"it's not a number\" before the branch spec","user":{"login":"dalpert-korewireless","id":10949053,"avatar_url":"https://avatars.githubusercontent.com/u/10949053?v=3","gravatar_id":"","url":"https://api.github.com/users/dalpert-korewireless","html_url":"https://github.com/dalpert-korewireless","followers_url":"https://api.github.com/users/dalpert-korewireless/followers","following_url":"https://api.github.com/users/dalpert-korewireless/following{/other_user}","gists_url":"https://api.github.com/users/dalpert-korewireless/gists{/gist_id}","starred_url":"https://api.github.com/users/dalpert-korewireless/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dalpert-korewireless/subscriptions","organizations_url":"https://api.github.com/users/dalpert-korewireless/orgs","repos_url":"https://api.github.com/users/dalpert-korewireless/repos","events_url":"https://api.github.com/users/dalpert-korewireless/events{/privacy}","received_events_url":"https://api.github.com/users/dalpert-korewireless/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-01-15T17:26:51Z","updated_at":"2016-01-15T17:26:51Z","closed_at":null,"body":"Given I install Git for Windows 2.7.0\r\nAnd open a bash shell\r\nAnd change into a git working directory\r\nWhen I press `<enter>` at a command prompt\r\nThen I expect to see the next command prompt right away.\r\n\r\nInstead, I was seeing the command shell pause to read input from the command line.\r\n\r\nThen, based on whether that input was parseable to a number or not, the prompt would\r\nprint out \"it's a number\" or \"it's not a number\" as part of the decoration configured by PS1\r\nout of the box (see example session below)\r\n\r\n````\r\nDAlpert@machine-name MINGW64 /d/dev/git/repo-nameit's not a number (patch-8.21.3)\r\n$ <enter>\r\n<enter>\r\nDAlpert@machine-name MINGW64 /d/dev/git/repo-nameit's not a number (patch-8.21.3)\r\n$ <enter>\r\n4<enter>\r\nDAlpert@machine-name MINGW64 /d/dev/git/repo-nameit's a number (patch-8.21.3)\r\n$\r\n````\r\n\r\nThis took a while to track down as initially I didn't realize it was waiting on input but\r\nrather wondered if the newest version of Git for Windows shell had introduced an \r\ninterpreter-like requirement to press `<enter>` twice after every command.\r\n\r\nThis is particularly confusing when entering a command like a directory listing and\r\nwondering why it was not returning me to the command prompt until after I pressed\r\n<enter> again.\r\n\r\nUsing a manual form of `git bisect` I was able to trace the source of this behavior \r\nto [this line in `git-prompt.sh`](https://github.com/git-for-windows/git/blob/v2.7.0/contrib/completion/git-prompt.sh#L433)"}}