github动作徽章没有状态
我已经在我的存储库上进行了很多次github动作，没有问题，并且在我的一个存储库中使用相同的脚本显示“无状态”。 仓库是： https://github.com/aurelpere/aurelpere/python-planif
我不明白为什么当工作流正确运行时，它没有显示状态... 任何帮助都很棒 谢谢
注意到我的SVG徽章还显示了 https：/ /Github.com/aurelpere/python-planif/workflows/ci/badge.svg 和 https://github.com/aurelpere/python-planif/workflows/unittests/badge.svg 。 （遵循本文中的内容： https://github.community/t/badge-shows-no-status-and-no-status-and-no-status-no-status-mismatch-bet------------------------------s--------------------------------- /a>或在这篇文章中
我还试图在另一个新鲜仓库中复制代码（ https：/https：// /Github.com/aurelpere/python-geothermal-- power-to-to-gas/ ）而且是一样的，徽章没有任何状态，因此它与此处的快进融合问题无关， https://github.community/t/workflow-badge-no-status/17280/2
编辑：以下面的答案解决了，但我删除了初始存储库如果您尝试遵循链接，只保留新鲜的
I have run many times github actions on my repo without problem and with the same script on one of my repo it is displaying “no status”.
The repo is: https://github.com/aurelpere/python-planif
I dont understand why it is not displaying a status as the workflow runs correctly…
Any help would be great
thank you
Notice my svg badge also shows "no status" at https://github.com/aurelpere/python-planif/workflows/CI/badge.svg and at https://github.com/aurelpere/python-planif/workflows/Unittests/badge.svg .
(following what is in this post : https://github.community/t/badge-shows-no-status-and-no-status-mismatch-between-the-filepath-vs-name-usage/16907 or in this post Github Actions badge shows "No status")
I also tried to duplicate the code in another fresh repo (https://github.com/aurelpere/python-geothermal---power-to-gas/
) and it is the same, the badge shows no status, so it has nothing to do with the fast forward merge issue from here https://github.community/t/workflow-badge-no-status/17280/2
Edit : solved with the answer below, but i deleted the initial repo and kept only the fresh one if you try to follow the links
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
由于某种原因，您必须使用工作流名代替YAML文件名。这对我有用
For some reason you have to use the workflow name instead of the yaml file name. This worked for me