[pulsar-site] branch main updated: [fix] ready-to-test is not applicible for docs only changes (#328)

[ti...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

tison pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/pulsar-site.git


The following commit(s) were added to refs/heads/main by this push:
     new b502bda388a [fix] ready-to-test is not applicible for docs only changes (#328)
b502bda388a is described below

commit b502bda388a38025ae0dc658e491032ab5d17ab2
Author: tison <wa...@gmail.com>
AuthorDate: Tue Dec 13 23:08:59 2022 +0800

    [fix] ready-to-test is not applicible for docs only changes (#328)
    
    Signed-off-by: tison <wa...@gmail.com>
    Co-authored-by: Anonymitaet <50...@users.noreply.github.com>
---
 site2/website-next/contribute/develop-labels.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/site2/website-next/contribute/develop-labels.md b/site2/website-next/contribute/develop-labels.md
index cd89dd18938..9be9c54d1a6 100644
--- a/site2/website-next/contribute/develop-labels.md
+++ b/site2/website-next/contribute/develop-labels.md
@@ -7,7 +7,7 @@ This guide explains the labels used in the [apache/pulsar](http://github.com/apa
 
 ## ready-to-test
 
-After [PR-17693](https://github.com/apache/pulsar/pull/17693) merged, pull requests should be first tested in your own fork since the pulsar CI based on GitHub Actions has constrained resources and quota. GitHub Actions provides separate quota for pull requests that are executed in a forked repository.
+After [PR-17693](https://github.com/apache/pulsar/pull/17693) merged, pull requests **except [docs only changes](https://github.com/apache/pulsar/blob/master/.github/changes-filter.yaml#L5)** should be first tested in your own fork since the pulsar CI based on GitHub Actions has constrained resources and quota. GitHub Actions provides separate quota for pull requests that are executed in a forked repository.
 
 When a committer believe the PR is ready to test, they will label `ready-to-test` to the PR, and then you can rerun the CI tasks by commenting `/pulsarbot run-failure-checks` and trigger the full CI validation.