Workflow badge "no status" #25097
-
I followed the documentation, but I have one of two badges that shows “no status”. Is this a bug? Repo: https://github.com/algosphere/algo-website Code:
It’s ok for develop but “no status” for master. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
I checked your master/ develop branch commits history. It seems that when you merge from develop branch to master branch, it used fast-forward merge. This is a known issue. Please check the previous tickets: https://github.community/t5/GitHub-Actions/Actions-Reporting-Wrong-Branch-on-Merges/td-p/36966 https://github.community/t5/GitHub-Actions/Wrong-branch-displayed-for-workflow/m-p/37985#M3178 I would encourage you to merge using pull request , when it is merged, there will be a merged commit push to master. This could avoid this issue. |
Beta Was this translation helpful? Give feedback.
-
Ok thanks @yanjingzhu, I look forward to a fix then. Thanks for the recommandation though! |
Beta Was this translation helpful? Give feedback.
I checked your master/ develop branch commits history. It seems that when you merge from develop branch to master branch, it used fast-forward merge.
This is a known issue. Please check the previous tickets:
https://github.community/t5/GitHub-Actions/Workflow-badge-always-quot-no-status-quot-when-limited-to-branch/td-p/40051
https://github.community/t5/GitHub-Actions/Actions-Reporting-Wrong-Branch-on-Merges/td-p/36966
https://github.community/t5/GitHub-Actions/Wrong-branch-displayed-for-workflow/m-p/37985#M3178
I would encourage you to merge using pull request , when it is merged, there will be a merged commit push to master. This could avoid this issue.