Remove/disable assets workflow #7800
Comments
|
👋 @sk593 Thanks for filing this bug report. A project maintainer will review this report and get back to you soon. If you'd like immediate help troubleshooting, please visit our Discord server. For more information on our triage process please visit our triage overview |
|
Related issue: #7780. |
|
I think removing is the way to go if we are sure that the assets generated are not being used. cc/ @willdavsmith |
|
We've disabled this for now. We'll go ahead with the delete if there's no unexpected issues |
|
👍 We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up. We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue. For more information on our triage process please visit our triage overview |
# Description Cleaning up disabled workflow assets.yaml. ## Type of change - This pull request is a minor refactor, code cleanup, test improvement, or other maintenance task and doesn't change the functionality of Radius (radius-project#7800 ). Fixes: radius-project#7800 Signed-off-by: Reshma Abdul Rahim <[email protected]>
Steps to reproduce
The assets workflow has started to fail. We don't use any of the assets that get uploaded so these should be disabled and/or removed: https://github.com/radius-project/radius/blob/main/.github/workflows/assets.yaml
Observed behavior
No response
Desired behavior
Either we disable and eventually delete the workflow or we update the workflow so it passes. We don't pull assets from Azure storage anymore so this shouldn't be needed
Workaround
No response
rad Version
GH actions runs
Operating system
No response
Additional context
No response
Would you like to support us?
AB#12960
The text was updated successfully, but these errors were encountered: