Correct error message when destroying projects without force #492
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Radoslaw Kutylowski <[email protected]>
Radoslaw-Kutylowski
force-pushed
the
fix/wrong_message_on_no_force_destroy
branch
from
11590eb to
35c68b9
Compare
flbla
approved these changes
Feb 3, 2025
|
@Radoslaw-Kutylowski thank you |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The error message shown when trying to destroy a non-empty project asked to set
force_deleteto true, but no such variable is available. The PR corrects the message to sayforce_destroyinstead.