I'm not quite sure how you can say GitHub has a superior information hierarchy when it's flat from first principles. GitLab allows nested groups as you'd expect

I'm not quite sure how you can say GitHub has a superior information hierarchy when it's flat from first principles. GitLab allows nested groups as you'd expect from any modern filesystem but there's just no equivalent in GitHub. I've found that philosophy has followed to actions output. I can pretty easily follow the DAG shown in any GitLab pipeline view, but GitHub just gives me a sequential list of jobs on the left and I'm left to just remember whether any of them were dependent on previous jobs else go read the code to figure that out. Maybe it's just familiarity, as I've self hosted GitLab and its CI for years before actions were a thing, to the tune of nearly 8 years now. Personally, I was really disappointed in the implementation and the UX/DX of Actions as their own brand new construct rather than a DSL for gluing together the shell commands you already run on your dev machine.