xuxiaowei-com-cn opened a new issue, #8058:
URL: https://github.com/apache/incubator-seata/issues/8058

   ### Check Ahead
   
   - [x] I have searched the [issues](https://github.com/seata/seata/issues) of 
this repository and believe that this is not a duplicate.
   
   - [x] I am willing to try to fix this bug myself.
   
   
   ### Ⅰ. Issue Description
   
   # English
   
   1. Fork the project, then enable Actions.  
   2. Every time code is pushed, `.github/workflows/publish-ossrh.yml` is 
triggered, and this Actions workflow has syntax errors.  
   3. Even if `.github/workflows/publish-ossrh.yml` is disabled, the next code 
push will automatically re-enable it, resulting in Actions errors again.  
   4. Each error sends an email, which greatly affects contributors.  
   5. Speculated reason: The inspection rules for projects (Actions) created at 
different times are different.
   
   # 中文
   
   1. fork 项目,之后启用 actions。
   2. 每次推送代码都会触发 .github/workflows/publish-ossrh.yml ,而该 actions 语法错误。
   3. 即使禁用了 .github/workflows/publish-ossrh.yml ,下次推送代码,还会自动启用,出现 actions 错误。
   4. 每次错误都会发送邮件,非常影响贡献者。
   5. 推测原因:不同时间创建的项目(actions)的检查规则不同。
   
   <img width="2092" height="1229" alt="Image" 
src="https://github.com/user-attachments/assets/6d30a3fa-b16e-4bef-8e9b-57e8356e7fc9";
 />
   
   ### Ⅱ. Describe what happened
   
   _No response_
   
   ### Ⅲ. Describe what you expected to happen
   
   _No response_
   
   ### Ⅳ. How to reproduce it (as minimally and precisely as possible)
   
   _No response_
   
   ### Ⅴ. Anything else we need to know?
   
   _No response_
   
   ### Ⅵ. Environment
   
   _No response_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to