Replies: 1 comment
-
Actually, here some examples where the two routes show a different status value for the same repo https://github.com/NextAudio/NextAudio/workflows/.NET/badge.svg https://github.com/NextAudio/NextAudio/workflows/.NET/badge.svg?branch=main Reproduces at 19:44 UTC, 21 September 2022. Might change with repo activity. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello.
There are two different routes for GitHub Workflow Status badges. For example
https://github.com/exoRift/react-fluent-mobile/workflows/Quality%20Assurance/badge.svg?branch=master
https://github.com/exoRift/react-fluent-mobile/actions/workflows/quality_assurance.yml/badge.svg?branch=master
The one that uses the
/workflows
route with workflow name as a param is the "old" route, whereas/actions/workflows
with the workflow filename is the "new" route. We can see in the github docs repo this was changed in the documentation in github/docs@f9b50ac but there is not really any info in the commit message explaining why the change was made and the linked issue in the commit message is a 404.Anecdotally, we have seen that sometimes the two different badge routes may produce different results. You will probably find that
https://github.com/Wandalen/wTools/workflows/mod_interface/badge.svg?branch=master
https://github.com/Wandalen/wTools/actions/workflows/ModuleModInterfacePush.yml/badge.svg?branch=master
currently serve the same result, but we've seen situations where they don't match:
I might be able to reproduce this if it helps, but possibly only for a short amount of time.
The key questions I have are: Should these two routes be serving the same information? If not, what is the difference?
Beta Was this translation helpful? Give feedback.
All reactions