101–110 of 124 posts
We're going to enter the era of returning to self hosting. Self hosted gitlab is a dream, no surprises ever, exactly how your repos are supposed to work.
I'm all for self-hosting btw, we do it at my company. But it's not as easy as you make it sound.
Earlier quoted context omitted.
> In proper tools that are designed to solve a specific need, not try to do everything: badly. And when you want to search for that one thing that you know got documented somewhere, but can't remember where, how many systems do you have to search? That's one of the reasons I like the code, issues, docs (code or wiki depending), and discussions all in the same repo. Not to be confused with Chat, which is more ephemera…
> And when you want to search for that one thing that you know got documented somewhere, but can't remember where, how many systems do you have to search? Not GP, but is that actually a real problem? Take a project like OpenBSD where the code, the bug tracking , and the design discussion happens in different place? Even in reality, you don’t put the workshop in the conference room.
I've done consulting with bigger orgs (Fortune 500) and the more systems they have the harder it is to find things. It's a problem for them too.
So..in short, yes it's a real problem.
Earlier quoted context omitted.
Where do you keep Issues, Pull Requests, Wikis, Discussions, project boards, and everything else? (rhetorical question.) These days, the problem with cloud-hosted Git platforms is not where to push your code. Replicating repositories across multiple providers is relatively easy, and Git has always been good at that. The harder problem is that successful teams end up accumulating a lot more than source code around the…
(I upvoted you, for asking the real questions, but to answer) > Where do you keep Issues, Youtrack > Pull Requests, Gerrit, it's way better for code review > Wikis, Also Youtrack, but other software exists that's specific for this, I have seen Confluence used a lot and while I don't recommend: that's usually the case. > Discussions, As far away from code as possible, right now it's Zulip > project boards, Youtrack, t…
And then for Youtrack, Jira, Confluence, etc. You still have the same problem where it is difficult to migrate to a different system, because the data is all stored in a proprietary format that can't easily be ported to something else. For the wiki, there are somewhat standard formats used by multiple systems, like markdown and mediawiki. But for issues, I don't know of any standardized format, and migrating from one product to another is going to be pretty difficult.
Author here. For those who don't care for the color scheme, my site has - a light theme: https://eblog.fly.dev/githubbad-light.html - a plain theme: https://eblog.fly.dev/githubbad-plain.html , added as part of the same update where I submitted this article. Both of those are available as PDFs as well (replace .html with .pdf). And of course you can use reader mode in your favorite browser.
> The increased ‘agentic’ load on github is the direct result of their own actions and those of their parent company, Microsoft, and that makes reliability problems their own fault. Microsoft & Github are not a monolith. it's an institution with dozens of divisions and 100k+ employees all vying for revenue. Anyone who's worked at a big company knows what it's like to be given an unfunded mandate to serve an important…
Author here. I am not a free GitHub customer. The only times I use GitHub are when my consulting clients do, who are by and large GitHub enterprise customers. It is not entitlement to complain about a company that you pay money for a service failing to provide that service by the terms of their own service lifetime agreement, something I point out repeatedly.
Earlier quoted context omitted.
Where do you keep Issues, Pull Requests, Wikis, Discussions, project boards, and everything else? (rhetorical question.) These days, the problem with cloud-hosted Git platforms is not where to push your code. Replicating repositories across multiple providers is relatively easy, and Git has always been good at that. The harder problem is that successful teams end up accumulating a lot more than source code around the…
(I upvoted you, for asking the real questions, but to answer) > Where do you keep Issues, Youtrack > Pull Requests, Gerrit, it's way better for code review > Wikis, Also Youtrack, but other software exists that's specific for this, I have seen Confluence used a lot and while I don't recommend: that's usually the case. > Discussions, As far away from code as possible, right now it's Zulip > project boards, Youtrack, t…
Not really, it sounds you made a mess of things by having to rely on a dozen small disjointed services and separate account and auth needs instead of just using a single integrated environment.
There are many reasons why a service like GitHub is really not about git.
Earlier quoted context omitted.
Author here. I am not a free GitHub customer. The only times I use GitHub are when my consulting clients do, who are by and large GitHub enterprise customers. It is not entitlement to complain about a company that you pay money for a service failing to provide that service by the terms of their own service lifetime agreement, something I point out repeatedly.
That is helpful context, thank you for now sharing. So it sounds like you’re not a paying customer, and that your report & experiments were completed from a free customer account, right? If that’s not the case, it would be helpful context to add to your report. How can someone only use GitHub on behalf of their clients? Perhaps you mean it in the narrow sense of “I don’t have any private GitHub repos myself”, rather…
Before I went independent I used GitHub for a bunch of different employers, so I've watched it's decline over the last decade from the front row.
My clients are the ones paying for GitHub enterprise, in this case. Depending on the context I'll either use my personal account or an account under their organization, etc. Usually I don't have admin permissions (rightfully!), sometimes I do.
I have used pretty much every corner of GitHub in pretty much every possible context for well over a decade. I'm sure you could find something I haven't touched, but you'd have to think pretty hard. I thought that would be obvious from the fact I talked about things like SLAs and GitHub actions, but I guess I should have been clearer.
My company recently forced us to move from Atlassian BitBucket to GitHUb. What a mess.
Earlier quoted context omitted.
(I upvoted you, for asking the real questions, but to answer) > Where do you keep Issues, Youtrack > Pull Requests, Gerrit, it's way better for code review > Wikis, Also Youtrack, but other software exists that's specific for this, I have seen Confluence used a lot and while I don't recommend: that's usually the case. > Discussions, As far away from code as possible, right now it's Zulip > project boards, Youtrack, t…
> Now, a sane person will respond to me with the fact that I haven't removed any single points of failure, I've actually just added more of them. They'd be right! The differences is that it makes the stack a bit more flexible and composable. Not really, it sounds you made a mess of things by having to rely on a dozen small disjointed services and separate account and auth needs instead of just using a single integrat…