I am not sure if this is a bug, missing feature or if I simply cannot find the button. I want to remove a file from a release. How can I do that (without deleting the whole release and recreate it)?
Cannot remove asset file from release #416
Yeah, looks like you cannot remove files, but add new one. Not sure if it's really a bug, but it would be an improvement if this was possible.
Also noticed that uploading an empty file (0B) shows up as 1KB while files under 1KB are shown with their correct size in bytes ... interesting.
Update: Even better, uploading a 0B file actually creates a 1KB junk file filled with many zeroes ... 🤔 https://try.gitea.io/fnetx/testing-gitea-releases/releases/tag/r2
Update 2: The original is issue already reported upstream: https://github.com/go-gitea/gitea/issues/12963 (and PR is active, but WIP: https://github.com/go-gitea/gitea/pull/14130)
Well, one cannot even overwrite existing files. If you upload another file with the same name, this filenname shows up twice in the list.
Marking as enhancement, as it is possible to delete the complete release and re-create it?
(planned for gitea-1.15)
Heh, to delete is posible via API, witch mean only UI has to be made ...
And if I would understand JS better I would have already dine the replace if asset with same name exist
should be fixed - feel free to reopen if not
Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
Something is not working the way it should. Does not concern outages.
Errors evidently caused by infrastructure malfunctions or outages
This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
Please join the discussion and consider contributing a PR!
No bug, but an improvement to the docs or UI description will help
This issue or pull request already exists
New feature
Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
An issue directly involving legal compliance
involving questions about the ToS, especially licencing compliance
Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
Things related to Codeberg's external communication
More information is needed
This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
Related to Forgejo. Please also check Forgejo's issue tracker.
Migration related issues in Forgejo
Issues related to the Codeberg Pages feature
Issue is related to the Weblate instance at https://translate.codeberg.org
Woodpecker CI related issue
involves improvements to the sites security
Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
Codeberg's current set of contributors are not planning to spend time on delegating this issue.
No due date set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?