I DONT GIVE A FUCK ABOUT THE FUCKING CODE! i just want to download this stupid fucking application and use it.
https://github.com/torvalds/linux
WHY IS THERE CODE??? MAKE A FUCKING .EXE FILE AND GI...
I know it doesn’t address the issue for most people, but that and other things can be “fixed” with the refined GitHub extension.
The worst part IMO is that there used to be a “releases” button somewhere that got nuked. While “projects” is usually there, even though repos rarely use it.
It’s not just GitHub. Gitlab, Forgejo, etc., they all have releases hidden in a rather small tab instead of in a big obvious place where one might expect to see them.
They need to make it actively harder then because most devs with a site seem to just link direct to the release page. IMO, if that’s the thought process then either make it intuitive or commit and lock it down to contributors or something.
On Gitlab, it’s in the sidebar, in a submenu under “Deployment”. It could maybe be pulled up a level, but I’d argue that’s more findable than on Github
Because GitHub really doesn’t want to be the webhost for releases. They want you to spin up a website and provide downloads from your own server, and only link to github for the code.
GitHub’s layout is strange to me. Why isn’t releases in the top nav bar with Code, Issues, PR, etc.
I know it doesn’t address the issue for most people, but that and other things can be “fixed” with the refined GitHub extension.
The worst part IMO is that there used to be a “releases” button somewhere that got nuked. While “projects” is usually there, even though repos rarely use it.
It’s not just GitHub. Gitlab, Forgejo, etc., they all have releases hidden in a rather small tab instead of in a big obvious place where one might expect to see them.
Interesting. Maybe they don’t want to be an application hosting site to non-developer types by making releases easy to use.
They need to make it actively harder then because most devs with a site seem to just link direct to the release page. IMO, if that’s the thought process then either make it intuitive or commit and lock it down to contributors or something.
I think the other ones are just copying github
On Gitlab, it’s in the sidebar, in a submenu under “Deployment”. It could maybe be pulled up a level, but I’d argue that’s more findable than on Github
Because GitHub really doesn’t want to be the webhost for releases. They want you to spin up a website and provide downloads from your own server, and only link to github for the code.
Exactly!