Why does everyone keep their plugins in the repo and not publish them as a release on Github?

[bobbintb]

I noticed plugins that are hosted on Github all point to the "raw" link within the repo and nobody ever uses the release function in Github. I prefer to add artifacts as a release and not keeping them in the repo. I tested using the link from a release and I got a server error. I'm assuming that's the reason developers don't do it that way and there is a redirect or something that the plugin installer doesn't like. Is that the only reason it is done that way? Is it just a convention that someone started and everyone followed?

[itimpi]

I think the assumption is that the plugin are going to be installed via Community Applications and so no need to use the gitHub release feature as long as you do whatever CA needs to see a new version?  Not sure what advantage (if any) using the Release function would give to the average developer.

[SimonF]

18 minutes ago, bobbintb said:

I noticed plugins that are hosted on Github all point to the "raw" link within the repo and nobody ever uses the release function in Github. I prefer to add artifacts as a release and not keeping them in the repo. I tested using the link from a release and I got a server error. I'm assuming that's the reason developers don't do it that way and there is a redirect or something that the plugin installer doesn't like. Is that the only reason it is done that way? Is it just a convention that someone started and everyone followed?

I dont do releases.

[primeval_god]

2 hours ago, bobbintb said:

I noticed plugins that are hosted on Github all point to the "raw" link within the repo and nobody ever uses the release function in Github. I prefer to add artifacts as a release and not keeping them in the repo. I tested using the link from a release and I got a server error. I'm assuming that's the reason developers don't do it that way and there is a redirect or something that the plugin installer doesn't like. Is that the only reason it is done that way? Is it just a convention that someone started and everyone followed?

I use releases for the compose plugin and the swapfile plugin.

[ich777]

On 6/27/2024 at 6:52 PM, bobbintb said:

and nobody ever uses the release function in Github

I do that, but not for all plugins.

 

You can take a look at the Intel-GPU-TOP plugin for example here which is working just fine:

https://github.com/ich777/intel-gpu-top

 

My driver plugins utilize the Release section too for the driver packages, in combination with the "usual" packages directory for the plugin related files.

 

On 6/27/2024 at 6:52 PM, bobbintb said:

Is it just a convention that someone started and everyone followed?

I think it's this.

 

 

You also have to keep in mind that I have massive issues with users from China and the Release section or better speaking the API because by default I think it's blocked there. They have to use a proxy or VPN to circumvent that.

[Rysz]

Since 99% of users won't ever visit the GitHub repositories, it's more convenient to just work inside the file tree for me.