Yes it does, with the added ability to interact with conda.
Git Bash isn’t really necessary, but I tend to use it for Git and Github stuff on Windows. I just like the way it displays Git-related files and actions in different colors by default. I do occasionally use Git from Anaconda Prompt, but I just feel like the user experience is a little better from Git Bash.
The main draw of using Git Bash over Command Prompt is that you are using Bash. The commands are different and it is generally easier to use and more powerful than Command Prompt. Also, if you switch between operating systems like I do, knowing how to use the Bash command line is important since Windows is the only OS that uses Cmd. If you go back and forth between Windows and Mac or Linux, using Git Bash for your main Windows terminal means uniformity across platforms.
As I mentioned, on Windows I mostly use it for Git and Github-related actions. Outside of that, I stick to Anaconda Prompt for my Python work because I really enjoy using conda for installations and virtual environments and I didn’t feel like setting up conda in my Git Bash. It’s really all about preference. However, it can’t hurt to at least be familiar with Bash since there are very few Python developers that program exclusively on Windows.