[GitHub] [pulsar] lhotari commented on pull request #17693: [feat][CI] Add approval solution to reduce GitHub Actions resource consumption

[GitBox <gi...@apache.org>]

lhotari commented on PR #17693:
URL: https://github.com/apache/pulsar/pull/17693#issuecomment-1249308050

   Here's the latest example of the instructions that get printed as an error message and in the workflow summary:
   
   # Instructions for proceeding with the pull request:
   
   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/lhotari/pulsar and ensure that your branch is up to date with https://github.com/apache/pulsar
      Sync your fork if it's behind.
   2. Open a pull request to your own fork. You can use this link to create the pull request in
      your own fork:
      https://github.com/lhotari/pulsar/compare/master...lhotari:lh-pulsarci-ready-to-test?expand=1
   3. Edit the description of the pull request https://github.com/lhotari/pulsar/pull/83 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.
   
   If you have any trouble, please join the #contributor channel on Pulsar Slack to get real-time support.
   Instructions for joining Pulsar Slack: https://pulsar.apache.org/community#section-discussions
   


-- 
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-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org