fix: use json escape to allow any string in workflow name#96
Merged
edersonbrilhante merged 1 commit intomainfrom Aug 19, 2025
Merged
fix: use json escape to allow any string in workflow name#96edersonbrilhante merged 1 commit intomainfrom
edersonbrilhante merged 1 commit intomainfrom
Conversation
edersonbrilhante
force-pushed
the
fix-tag-ec2
branch
from
2f4dcfc to
0980d64
Compare
Rostislavz
approved these changes
Aug 19, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
This PR fixes hook job to allow tag ec2 instances with space and special characters in the workflow name
Type of Change
Checklist