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.
Runtime platform environment
Github Action
RocketMQ version
branch : develop
JDK Version
No response
Describe the Bug
The workflow retry mechanism fails to trigger because of recent changes to the repository's action permissions, which now default to read-only. This prevents the GH_TOKEN from having the necessary actions: write permission to trigger the retry mechanism.
Steps to Reproduce
Push a commit to trigger the workflow.
Allow the workflow to fail.
Observe that the retry mechanism is not triggered.
What Did You Expect to See?
The workflow retry mechanism should trigger after a failure, attempting to rerun the workflow
What Did You See Instead?
The workflow retry mechanism does not trigger because the GH_TOKEN does not have the required actions: write permission.
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.
Runtime platform environment
Github Action
RocketMQ version
branch : develop
JDK Version
No response
Describe the Bug
The workflow retry mechanism fails to trigger because of recent changes to the repository's action permissions, which now default to read-only. This prevents the GH_TOKEN from having the necessary actions: write permission to trigger the retry mechanism.
Steps to Reproduce
What Did You Expect to See?
The workflow retry mechanism should trigger after a failure, attempting to rerun the workflow
What Did You See Instead?
The workflow retry mechanism does not trigger because the GH_TOKEN does not have the required actions: write permission.
Additional Context
No response
The text was updated successfully, but these errors were encountered: