This is amazing insight - thank you so much for taking the time, I really mean it.
Let's see if I can stretch the friendship ;)
Would you say that it's fair to say that there's a common theme running under a few of this items which is that Github see's the Repo as the "core entity", and has everything else hanging off that (Project management, conversations, pipelines, etc).
Whereas something - lets say the Atlassian suite for example, more see's "projects" as that "core entity", and then has things like your code, pipelines, conversations, etc hanging off it?
Also a question on Github projects (and this may just be my ignorance), but are the projects in Github tightly coupled to certain repo's? I never liked Gitlabs project tooling because the "Project" was too tightly coupled to a repo, making it kinda jank when you were working on a project that touched multiple repo's.
Let's see if I can stretch the friendship ;)
Would you say that it's fair to say that there's a common theme running under a few of this items which is that Github see's the Repo as the "core entity", and has everything else hanging off that (Project management, conversations, pipelines, etc).
Whereas something - lets say the Atlassian suite for example, more see's "projects" as that "core entity", and then has things like your code, pipelines, conversations, etc hanging off it?
Also a question on Github projects (and this may just be my ignorance), but are the projects in Github tightly coupled to certain repo's? I never liked Gitlabs project tooling because the "Project" was too tightly coupled to a repo, making it kinda jank when you were working on a project that touched multiple repo's.