Handling of unwanted characters in workflow name
See original GitHub issueI have an emoji (⚒️) in a workflow name and this causes errors when Azure/k8s-deploy@v4.1
is done rolling out an deployment. Could we expose a option to optionally override the workflowFriendlyName
name, or an option to allow filtering out unwanted characters?
Error
Workflow name
I tried setting the environment variable GITHUB_WORKFLOW
but that did not do the trick.
- uses: Azure/k8s-deploy@v4.1
with:
[...]
env:
GITHUB_WORKFLOW: "foo"
Thanks!
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:6
Top Results From Across the Web
Flow: Stripping Unwanted Characters or Special ...
For those who may need a way to strip special characters from a string then here is a method using Microsoft Flow.
Read more >using variables to clean up disallowed characters in a file name
Hi @tbakrf,. Have a look at this solution from @AlanPs1. It is storing the invalid characters in an array and looping through the...
Read more >Dealing with special characters in branch and tag names
Most branch and tag names with special characters can be handled by including the name in single quotes, for example 'hello-$USER' . In...
Read more >Solved: Remove special characters - Designer
Solved: I would like to do what "Data Cleanings" function does and so remove special characters from a field with the formula function.For....
Read more >Solved: Re: How to avoid file attachments with "special ch...
There are a number of "special characters" that SharePoint will not allow in file/folder names (e.g. &, #, %). However, the browse function ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Created a release with the fix for v4. Thanks!
I’d prefer not to allow for a custom name. It would require another documented input and we already have a ton. Makes this action harder to understand.