default workflow name is not filename, but file path
Opened this issue · 12 comments
Wrote support about this:
https://help.github.com/en/articles/workflow-syntax-for-github-actions#name says that when no name: is given, GitHub Actions will use the "workflow's filename".
That's not quite the behavior I'm seeing:
That is, in fact, the workflow file path from the root.
The same applies to the url to the action status badge: this also requires the entire file path from the repo root: https://github.com/r-lib/ghactions/workflows/.github/workflows/main.yml/badge.svg
This is a bit weird:The docs are unclear/wrongit's unclear why this would be so; just using the filename would be more succinct, or the path from ./github/workflows, because by definitions, workflows have to exist in that place.The url for the action status badge, in particular, gets ugly.So, perhaps you could change the docs here or the behavior?
https://help.github.com/en/articles/workflow-syntax-for-github-actions#name says that when no
name:is given, GitHub Actions will use the "workflow's filename".
Since at least January of this year (I didn't check further), GitHub changed the text. It now says:
If you omit name, GitHub sets it to the workflow file path relative to the root of the repository.
Even after adding a name to the workflow, github continues to show the filepath as the name under the actions tab.
Happens to me also
The same here
Me too. It was working fine for months, then somehow some of my workflows' name changed to file path. I have put the name since the beginning.
Those workflows have workflow_dispatch with inputs. After they changed to file path, I cannot run them manually anymore through the web UI.
My bad. It turns out that the workflows have been modified and there's syntax error there. After fixing the error, the name shows up correctly.
I had the same issue, it was caused by adding a colon character in input description field (using quotes for whole description text). After removing colon it works fine.
I had the same issue, and the reason was the existence of a commented line(#) in my file.
Issue is open since 2019? Hellooo github team, you there??
Same issue on my project too