Skip to content

semi-random release attachment & delete attachment-files #7151

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
2 of 7 tasks
staukini opened this issue Jun 7, 2019 · 2 comments
Closed
2 of 7 tasks

semi-random release attachment & delete attachment-files #7151

staukini opened this issue Jun 7, 2019 · 2 comments

Comments

@staukini
Copy link

staukini commented Jun 7, 2019

  • Gitea version (or commit ref):
  • Git version:
  • Operating system:
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant

Description

Hello!
I've created a release-version for one of my git-repos a few weeks ago. Now - out of nowhere - there are some randome files attached to some releases (which I uploaded a long time ago for testing purposes).
I even can't reproduce this "bug" on my system, nor can tell where this connection comes from.
Is there a way to remove attachments from a release? (I can upload further files but can't delete them.)

Also I figured out that when I create a new release (with one/more attachments) under [...]/data/attachments the file-count raises but when I delete the whole release it doesn't sink and gitea doesn't delete files (which were connected to the deleted release) --> but same as #2618

@stale
Copy link

stale bot commented Aug 7, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale stale bot added the issue/stale label Aug 7, 2019
@stale
Copy link

stale bot commented Aug 21, 2019

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale stale bot closed this as completed Aug 21, 2019
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant