Adjustments to the metadata description #1558
Merged
Conversation
This file contains hidden or 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
The metadata is too long and has been shortened. The "- ZAP-Hosting.com documentation" part has been removed because it was cut off due to its length and is superfluous. This allows more characters to be used for the actual content of the description.
|
Build Successful! You can find a link to the downloadable artifact below.
|
Some description fields were missing quotation marks. This could cause YAML parsing or build errors when special characters (e.g. colon, dash, or quotes) appear in the value. All description values are now wrapped in quotes as a preventive measure to ensure consistent and safe metadata parsing.
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 metadata was too long and has been shortened. The "- ZAP-Hosting.com documentation" part has been removed because it was cut off due to its length and is superfluous. This allows more characters to be used for the actual content of the description.
Apart from that, some description fields were missing quotation marks. This could cause YAML parsing or build errors when special characters (e.g. colon, dash, or quotes) appear in the value. All description values are now wrapped in quotes as a preventive measure to ensure consistent and safe metadata parsing.