Currently, after EventMesh graduated from Incubator, all contributors who do not have write access to the repository need Maintainer approval for the CI to run after submitting a pull request. This has increased the workload for reviewers during the review process.
To address this issue, I propose adding an optional configuration to the contribution guidelines. This will kindly remind contributors to enable GitHub Actions in their forked repositories, allowing them to self-correct various errors and allowing reviewers to directly view the CI results on the right-hand side of commit message.
After clicking on "Detail," you will be redirected to the Actions page of the forked repository.
Currently, after EventMesh graduated from Incubator, all contributors who do not have write access to the repository need Maintainer approval for the CI to run after submitting a pull request. This has increased the workload for reviewers during the review process.
To address this issue, I propose adding an optional configuration to the contribution guidelines. This will kindly remind contributors to enable GitHub Actions in their forked repositories, allowing them to self-correct various errors and allowing reviewers to directly view the CI results on the right-hand side of commit message.
After clicking on "Detail," you will be redirected to the Actions page of the forked repository.