Replying to an earlier post

The right time to look elsewhere was when Microsoft bought it.

The next best time was when viable alternatives like GitLab and later, Codeberg appeared.

The next best time was when it became clear that they were stealing your code to feed into their sparkly autocomplete and were going to sell it back to you.

The next best time was when they dumped a bunch of vibecoded garbage into the codebase and killed the uptime.

The next best time is now.

You don’t even have to migrate all your stuff. Just start all your new projects on Codeberg, or GitLab, or something self-hosted. Once you get used to the new place, you can migrate your old stuff when you’re ready.

Replying to @⁨_hovi_@lemmy.world⁩

I could rant a lot about the GitHub UX, so here’s just the fairly obvious stuff on the repository page:

Red arrows mean duplicated information or duplicated navigational elements.
Green arrow means why the fuck do I have to tell our customers to click a random link in the middle of bumfuck nowhere, in order to download our software?

Replying to @⁨trem@lemmy.blahaj.zone⁩

Unpopular opinion, but most of that is duplicated information that makes sense to be duplicated because I’m not a machine that can scan the whole page and instantly get what I need.

Top right are action buttons, fork and stars on the center right let you see who else starred and forked the repo.

License information just makes sense to be in a repo summary, and it just happens that most license files are at the root and visible in the file tree.

I don’t see the top level stuff, you probably see that because you’re not authenticated, so github tries to “sell” itself for you.

I agree “releases” should be at the top though (it used to, and I use GitHub refined to bring it back), but having the latest one at a glance is nice and saved me a click many times.

Replying to an earlier post

I mean, yeah, it can make sense to duplicate information. That screenshot isn’t supposed to say that all of these should be deduplicated.
But you really gotta be cautious with duplication, because it makes everything else harder to find. And I would absolutely argue that GitHub has crossed the line where they duplicate too much, across the board. It feels like design-by-committee.

This is entirely anecdotal, but what really dumbfounded me while annotating that screenshot, is that I never actually read the links in that “About” section.
I’ve seen this page probably a thousand times already, but I had no idea that there’s an “Activity” link there, which actually seems like it could be useful. Nor a link to the README, to the CONTRIBUTING.md or for “Custom Properties” (whatever that is).
I had no idea how to report a repo until now, even though the link is apparently always on screen.

There’s just so much info there, and it’s presented like read-only info, not like navigation links, so I always just skipped over the lines that don’t have numbers in them. I also genuinely never tried clicking any of these lines before…

Replying to an earlier post

Yeah? You should still make a decision. If you want it possible to watch, star and fork the repo from any of the sub-pages, then that stuff has to live in that top ribbon.

But then you shouldn’t duplicate it into the Code sub-page. I’d work with split buttons, where you can look at who starred and you can add your own star, all from the same UI element. It would not even take up more space, since they do already display the count in the top ribbon as well.

Apparently this is how Codeberg does it (see e.g. this repo), so this might be where I have the idea from…

Replying to an earlier post

Thanks for the links. Documentation is definitely a problem. They’d have to be open to feedback on documentation. Threads on documentation improvement are often met with “it exists, what more do you want?” even if the feedback is “this and this is missing” 🤷

Anyway, I’ll check out the links and try to set something up. My usage of radicle is definitely what it could be because of the lack of notifications. I literally fire and forget my repos, patches and so on, because I haven’t found an easy way to be made aware of responses or incoming patches.

Replying to an earlier post

Replying to an earlier post

I filled out an IT helpdesk request last week because I couldn’t push any updates to GitHub. I was able to access the site, so I though my access token was retired since that happens every once in awhile.

Nope. It was GitHub. For some reason it couldn’t accept my push despite the website still being up. And I didn’t find out until the tech called the the next day and it worked when I tried to recreate it in front of them

Replying to an earlier post

There was a surprising number of repos there when I last looked, and their blog seems to show signs of life, so I don’t think it’s vaporware (at least not yet). But yeah, not easily being able to browse repos from the home page definitely sucks.

FWIW, you can see some recent activity scroll by from right to left on the front page, near the top, right below the hero section. You can click them to view some users and repos (example: tangled.org/mitchellh.com).

That’s the only way I see from the front page though, which is not great :/