In November 2024 Microsoft announced that Git would be made available in SQL Server Management Studio version 21 (https://techcommunity.microsoft.com/blog/sqlserver/announcing-sql-server-management-studio-ssms-21-preview-1-and-copilot-in-ssms/4286966)
Historically DBAs have had to make do with roll-your-own source control integration tools and a plethora of alternatives sprang up – Flyway, a migration-centric schema control system, was acquired and integrated to Redgate in 2019 (https://www.red-gate.com/blog/database-devops/redgate-embraces-open-source-with-its-ongoing-development-of-flyway); dbt supports schema definitions and integrates well to source control; VS users were long-familiar with being able to define and save DDL into SQL Server projects that integrated to git, but until now this functionality was missing from the primary tool of the SQL Server DBA.
Be warned, it’s not totally seamless. As Brent Ozar notes, some features are a little clunky. For example, your commits will always be made to a local set of repositories, and it’s up to you to raise the PR to push/merge into the origin, and you’ll do that by clicking through to Github itself (https://www.brentozar.com/archive/2024/12/how-to-use-github-in-ssms-v21/). Branch management seems a little ropey, needing you to keep on top of deleted branches too.
Don’t forget that source control in databases is designed for your object definitions, scripts and so on – unless you’re dealing with very small data sets, don’t neglect to back up your data too, as Github (even with LFS) has hard limitations on artefact sizes.