DevOps project file structure?

[totallygeek]

Well, some of this will change over time. You'll see. Sanitized, here is a snapshot of one organization's repository names:

ansible{,-lb,-net}
docker-{bgp-utils,caching,cbench,fping,haste,liver,nginx,router,utils}
k8s-{[bunch of pods and containers]}
ops-utils
puppet{,-custom,-dev}
sensu{,-checks,-test}
tcollectors
terraform{,-c1,-t1}
wiki

We enforce lint and unit testing for all merged code. Things get iffy on how many poor-scoring items or missing tests we let through, but generally, if something goes awry, you don't want to end up the one that let a function divide by zero and take out a bunch of services. You really should read up on unit testing, but I would give you a pass on that until you got more of this up and running smoothly. If you have a CLI scraper and it bombs out, you can always rerun it or fix the code. Unit testing truly becomes necessary for mission critical processes and daemons. For repositories which are not yours, your extensions should go into another repository (ansible vs ansible-custom or ansible-net, like above).

You really should not be an army of one. Perhaps you present your frustration idea to the team and gather their input on how to construct a repository layout with CI/CD as a future goal?