You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.
Programming Language of the Client
Not related to the specified programming language
Runtime Platform Environment
N/A
RocketMQ Version of the Client/Server
N/A
Run or Compiler Version
N/A
Describe the Bug
The current GitHub badge cannot accurately reflect the build status of each binding, and when we changed the trigger timing of each binding corresponding workflow to workflow_call, we can no longer directly obtain the build status of each workflow.
Steps to Reproduce
N/A
What Did You Expect to See?
Since the status of each binding cannot be directly displayed, we can directly display the overall state of all bindings.
What Did You See Instead?
Separate status of each binding.
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Before Creating the Bug Report
I found a bug, not just asking a question, which should be created in GitHub Discussions.
I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.
I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.
Programming Language of the Client
Not related to the specified programming language
Runtime Platform Environment
N/A
RocketMQ Version of the Client/Server
N/A
Run or Compiler Version
N/A
Describe the Bug
The current GitHub badge cannot accurately reflect the build status of each binding, and when we changed the trigger timing of each binding corresponding workflow to
workflow_call
, we can no longer directly obtain the build status of each workflow.Steps to Reproduce
N/A
What Did You Expect to See?
Since the status of each binding cannot be directly displayed, we can directly display the overall state of all bindings.
What Did You See Instead?
Separate status of each binding.
Additional Context
No response
The text was updated successfully, but these errors were encountered: