-
Notifications
You must be signed in to change notification settings - Fork 25
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
clean-assets: delete realease in case all assets need to be deleted #77
Comments
There were "only" about 820 files for clangarm64, it was able to delete them all in one go. |
lazka
changed the title
delete-assets: delete realease in case all assets need to be deleted
clean-assets: delete realease in case all assets need to be deleted
Jul 30, 2023
lazka
added a commit
to lazka/msys2-autobuild
that referenced
this issue
Jul 30, 2023
In case a release has hundreds of files that need to be deleted this requires quite a bit of time and also works against the API rate limiting. In case we want to delete all assets of an release just delete and re-create the whole release instead. Fixes msys2#77
lazka
added a commit
to lazka/msys2-autobuild
that referenced
this issue
Jul 30, 2023
In case a release has hundreds of files that need to be deleted this requires quite a bit of time and also works against the API rate limiting. In case we want to delete all assets of an release just delete and re-create the whole release instead. Fixes msys2#77
lazka
added a commit
that referenced
this issue
Jul 30, 2023
In case a release has hundreds of files that need to be deleted this requires quite a bit of time and also works against the API rate limiting. In case we want to delete all assets of an release just delete and re-create the whole release instead. Fixes #77
One thing to be aware of is that deleting and re-creating releases results in github sending notifications. I may unsubscribe from release notifications specifically if this happens very often... |
oh, good point |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For this Python rebuild we had >5000 files and requires manual fixing when we need to clean things up because we would hit the api limit 5 times.
In case every asset of a release is about to be deleted we could just delete the whole release instead.
The text was updated successfully, but these errors were encountered: