(First, thank you Coderberg, I'm making a lot of use of your service for private repos. I appreciate it very much! My repos will become public, at which point I'll make some donations, but at the moment I'm still in a testing (of Codeberg) phase.)
I'm making frequent (pre)releases of my own software in Coderberg, which I'm doing with curl and including prerelease:true, which is working very well.
I see that the automatically generated tar/zip files of, for example, my 'pin' module contain:
pin/bin/pin
pin/man/pin.1
pin/README.md
etc
I think more standard (for a tar.gz of a release) would be:
pin-1.0.99.1/bin/pin
pin-1.0.99.1/man/pin.1
pin-1.0.99.1/README.md
etc
But I don't mind about that as I can work around it: I upload my own tar.gz file instead. But then I still see the automatically generated one. So then I edit the release page and enable "Hide automatically generated archives".
Would it be possible to extend the API so that this flag can be set via curl? Thanks!
### Comment
(First, thank you Coderberg, I'm making a lot of use of your service for private repos. I appreciate it very much! My repos will become public, at which point I'll make some donations, but at the moment I'm still in a testing (of Codeberg) phase.)
I'm making frequent (pre)releases of my own software in Coderberg, which I'm doing with curl and including ```prerelease:true```, which is working very well.
I see that the automatically generated tar/zip files of, for example, my 'pin' module contain:
```
pin/bin/pin
pin/man/pin.1
pin/README.md
etc
```
I think more standard (for a tar.gz of a release) would be:
```
pin-1.0.99.1/bin/pin
pin-1.0.99.1/man/pin.1
pin-1.0.99.1/README.md
etc
```
But I don't mind about that as I can work around it: I upload my own tar.gz file instead. But then I still see the automatically generated one. So then I edit the release page and enable "Hide automatically generated archives".
Would it be possible to extend the API so that this flag can be set via curl? Thanks!