-
Notifications
You must be signed in to change notification settings - Fork 253
Added safeguards around release pipeline #3296
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
base: main
Are you sure you want to change the base?
Conversation
Co-authored-by: Copilot <[email protected]>
…into wendi/fix-1es-pipeline pull.
…re-storage-azcopy into wendi/fix-1es-pipeline pull
…re-storage-azcopy into wendi/fix-1es-pipeline pull.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds safeguards to prevent accidental overwriting of existing releases in the AzCopy release pipeline by changing the GitHub release action from 'edit' to 'create', which will fail if a release already exists.
Key Changes
- Changed GitHub release action from 'edit' to 'create' to prevent overwriting existing releases
- Added explanatory comments about safe testing practices for the pipeline
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <[email protected]>
Description
Releases should not be overwritten after release :)
Feature / Bug Fix: (Brief description of the feature or issue being addressed)
Related Links:
PBI Item
Type of Change
How Has This Been Tested?
Thank you for your contribution to AzCopy!