Update nuget_build_release.yml to prevent character escaping #314
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.
I'm glad to see the workflow worked flawlessly, however I noticed in the logs that during the release file creation the GitHub Action executed commands that did not exist. These commands were text surrounded by ``. This had the consequence of removing them from the release file, which made weird sentences on the NuGet release notes.
But more importantly, this may compromise the build workflow if you accidentally were to include any kind of ill-intended string in your release body. While linux and bash systems are not my zone of confort, I managed to find a way to create that file in a way that should ignore escape characters, or, at least, those surrounded by ``.