As far as "good enough training to find a good position" if you want an "engineer" job title, get a masters degree from an Accreditation Board of Engineering Technologies (ABET) program. You should be able to do this in two years part time study at a local state engineering school. All state engineering schools are approximately equal in this regard.
My process lends itself to function block programming so generating useful diffs requires quite a lot of effort.
Siemens's TIA Portal you can export the source code to make it readable in git as long as you code in SCL (structured control language, which is really structured text), but it's not automatic and a lot of times the binary blob that is the source code and the exported readable code get out of sync cuz of lack of discipline by the programmer.
Rockwell's Studio 5000 can be readable if you use STL (structured text), may be this has changed though, I haven't used it in a long time.
Programming experiences in the industrial controls world is highly dependent on the brand/platform, the IEC 61131-3 describes the standards for industrial controls programming languages, but each brand implements them in a different way so there really is no standard. Writing structured text in one platform does not guarantee the same code will work in a different platform.
I've been working in this field for quite awhile and the systems can be complex and challenging. The software you write controls equipment that can cause massive damage and even death. This leads to very conservative programming languages and frameworks.
There are also industrial robot programmers who come straight out of high school, get some quick training and go to automotive integrators who contract them out to large automotive companies. This usually requires less engineering knowledge because the industrial robot platforms are relatively easy to learn and what you're doing most of the time is teaching the robot where to go to meet cycle times which is tedious, you use a "pendant" not a laptop usually, but that's changing with all the offline programming software, but reality never matches the simulation.
There reason most people don't like this field is you have to be in the "field", sometimes that's a loud ass, highly dangerous, manufacturing floor, outside in the searing heat or frigid cold, working with people that are.....uh...not the brightest, and work under constant pressure since "controls" is usually the last to get all the specs and the time you get to finish got shortened due to late deliverables from mechanical and electrical. It's not a job you can really do remotely. You can program remotely, but at some point your going to test you code on the machine and you're responsible for not breaking anything or killing anyone.
Finding people who are willing to do proper root cause analysis and not make wild assumptions about everything is pretty much the only important concern for onboarding in most manufacturing*system roles.
You will learn on the job. Go in with an open mind and try to remain humble. Pay will suck at first, but these domains are pretty much limitless in your career potential. I knew of some working in the photolithography area that were virtually classified as a nation state asset. Make yourself that important. You won't get that from college or a certification program. You get that by working with real tools in a real factory and learning about all the strange emergent properties of these systems as they come together.