-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stop auto block PRs #18
Comments
Thank you for the feedback. https://github.com/kcl-lang/kpm/blob/main/.github/workflows/cla.yml#L22 Do you mean this option? Sorry, I didn't notice it before. I should have deleted this configuration to solve the problem of automatic locking of the GitHub bot. |
It works fine in this PR kcl-lang/modules#123 Thank you! ❤️ |
Hey @liangyuanpeng @Peefy, |
Hey @Peefy , sorry it's been time i lost track of this issue, have made the PRs for the open issues, for the kcl-openapi one, there was no need of changing as the "lock-pullrequest-aftermerge" was already set to false. |
@Nivedita-coder @d4v1d03 |
Enhancement
Now, the PR will auto block by github action bot and the reason is KCL using github action of CLA to access and update information.
I have tested on my fork repo : https://github.com/liangyuanpeng/kpm/pulls?q=is%3Apr+is%3Aclosed
The first PR is working for reproduce auto block PR. And then PR would not be auto block after i delete the github action CLA,
For CLA, maybe you can try to https://github.com/cla-assistant/cla-assistant?tab=readme-ov-file#setup-your-own-instance-of-cla-assistant
@Peefy @zong-zhe
Summary
Set
lock-pullrequest-aftermerge
to false for disable auto block PR, you can find it at.github/workflows/cla.yaml
The text was updated successfully, but these errors were encountered: