lhotari commented on PR #23078: URL: https://github.com/apache/pulsar/pull/23078#issuecomment-2257705048
I'd recommend running tests for this PR in your own fork so that you get CI feedback without consuming apache/pulsar CI resources. apache/pulsar pull requests should be first tested in your own fork since the apache/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. > 1. Go to https://github.com/cognitree/pulsar/tree/master and ensure that your master branch is up to date > with https://github.com/apache/pulsar \ > [Sync your fork if it's behind.](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork) > 2. Open a pull request to your own fork. You can use this link to create the pull request in > your own fork: > [Create PR in fork for running tests](https://github.com/cognitree/pulsar/compare/master...cognitree:debezium-upgrade?expand=1&title=%5Brun-tests%5D%20%5Bfix%5D%5Bio%5D%20Upgrade%20Debezium%20connector%20version%20to%202.6.1.Final&body=This%20PR%20is%20for%20running%20tests%20for%20upstream%20PR%20https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar%2Fpull%2F23078.%0A%0A%3C!--%20Before%20creating%20this%20PR%2C%20please%20ensure%20that%20the%20fork%20https%3A%2F%2Fgithub.com%2Fcognitree%2Fpulsar%20is%20up%20to%20date%20with%20https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar%20--%3E) > 3. Edit the description of the pull request https://github.com/apache/pulsar/pull/23078 and add the link to the PR that you opened to your own fork > so that the reviewer can verify that tests pass in your own fork. > 4. Ensure that tests pass in your own fork. Your own fork will be used to run the tests during the PR review > and any changes made during the review. You as a PR author are responsible for following up on test failures. > Please report any flaky tests as new issues at https://github.com/apache/pulsar/issues > after checking that the flaky test isn't already reported. > 5. When the PR is approved, it will be possible to restart the Pulsar CI workflow within apache/pulsar > repository by adding a comment "/pulsarbot rerun-failure-checks" to the PR. > An alternative for the PR approval is to add a ready-to-test label to the PR. This can be done > by Apache Pulsar committers. > 6. When tests pass on the apache/pulsar side, the PR can be merged by a Apache Pulsar Committer. -- 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: commits-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
