Thanks @AstonJ.
We are currently running bare git repos, some ad-hoc git hooks and an old jenkins server. I am not happy with this and want to explore alternatives and a more integrated solution.
The hard thing is coming up with a solution that works for the entire team. There are some that are beginner git users and not familiar with github workflows.
We have a pretty “subversion” workflow going on at the moment. Everyone has commit rights to trunk and quite often commits break the build or tests (but in my opinion then it is too late). Here I want to add some sort of code review and a CI build step that runs the builds and tests before accepting the merge to trunk.
I know this can be setup with just git and other 3rd party software but I think a more prescriptive solution might be in order. Something that gives a little bit more to lean on.
Would be interesting to hear about GitLab but as an old sys-op I have lots of prejudice against it, so it is an uphill battle 