Git

In practice that means branching that fits a release cadence, resolving conflicts, review in pull requests, and pipelines that a push triggers. Jenkins and other CI systems belong in the same sentence for exactly that reason, since the value of the commit is what happens after it.

Game projects add a wrinkle, and it is why Perforce keeps appearing beside Git: large binary assets do not merge, and a repository of art and audio behaves nothing like one of source code. Studios answer that with Git LFS, or by keeping art in Perforce and code in Git. A requirement naming both describes that split.

For programmers the expectation is daily, fluent use. For artists and designers it is enough to commit work, fetch the current state and not break a branch - which is a lower bar, and still a stated requirement.