It seems to me you're confusing things again. A lot depends on company size and structure, but - given a reasonably sized enterprise - for the most part a software engineer takes specs and writes code meeting those specs from the dev perspective, then QA tests the release from the user perspective, and devops actually publishes the release to wherever. Of course the smaller an enterprise is, the more roles a single person will have.
But something like fully configuring a git repo isn't really the concern of a software engineer, per se; their concern is to create code that works, and git is just something to help with managing and passing on their creation. It's the one with the devops role who's really responsible for publication aspects (of course the same person may be doing both creation and publication) and should be ensuring repos don't have things committed which shouldn't be published (or even security if that's a separate role).
> Dario has gone out and said [...]
Different person from Cherny, but also I don't see anyone giving reasonable arguments as to why his prediction may be incorrect, only a lot of outrage. And I'm inclined to agree that AI will be able to do a lot of jobs; it's already on the way with quite a few, for example the software engineer role. I for one have been successfully using Claude Code for said role, while I handle the other aspects, and as it becomes good enough at other things I'll keep handing off more of the software production process to it.