-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Deleting container images is non-deterministic #25559
Comments
There may be a misunderstanding. You only delete a package version from the ui. If there are multiple versions the package is still there and you can view it from the package list. It may be better to redirect to the package again if there is still another version than the redirect to the package list after the delete. |
Okay, if that's the case, then we should probably indicate that you only delete the latest version by "deleting the package". |
Related #25559 Current behaviour: 1. Deletion of a package version 2. Redirect to the owners package list New behaviour: 1. Deletion of a package version 2.1. If there are more versions available, redirect to the package again 2.2. If there are no versions available, redirect to the owners package list
Related go-gitea#25559 Current behaviour: 1. Deletion of a package version 2. Redirect to the owners package list New behaviour: 1. Deletion of a package version 2.1. If there are more versions available, redirect to the package again 2.2. If there are no versions available, redirect to the owners package list
Related #25559 Current behaviour: 1. Deletion of a package version 2. Redirect to the owners package list New behaviour: 1. Deletion of a package version 2.1. If there are more versions available, redirect to the package again 2.2. If there are no versions available, redirect to the owners package list
As shown in my dupe issue, the wording needs some work. I was apprehensive to click that button because I assumed it would delete the entire package, instead of just a specific version. Since I never clicked the button, I never saw the wording shown in the image above, and assumed it's not possible to delete a specific version. |
Probably too late to add more ideas, but what would be the best UX is to have a small delete button next to each version, on the "view all" versions page: EDIT: |
Description
At the moment, it is only somewhat possible to delete
container
packages:When you come from the org
packages
tab and click ondelete
for any package, you simply get redirected to the org page listing all packages.When you come from the repo
packages
tab, there is a chance of about 50-60% that you will get the same behavior as with the orgpackages
tab.However, after trying about three to four times per package, I was finally able to delete one.
Gitea Version
1.19.3
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
Nothing. I mean, we only set the log level to
WARNING
, but apart from a lot of (somewhat) unrelated2023/06/28 11:23:44 ...les/cache/context.go:71:SetContextData() [W] [649bfc20] cannot get cache context when setting data: *db.Context.WithValue(type struct {}, val NotifyPackageDelete)
messages, there was nothing.Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
From binary.
Database
SQLite
The text was updated successfully, but these errors were encountered: