You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: SECURITY.md
+4
Original file line number
Diff line number
Diff line change
@@ -11,3 +11,7 @@ It is the responsibility of the security vulnerability handling project team (Ap
11
11
## Security Policy details and supported versions of Apache Pulsar
12
12
13
13
The security policy and supported versions are outlined on the Pulsar website under [Security > Security Policy and Supported Versions](https://pulsar.apache.org/docs/security-policy-and-supported-versions/).
14
+
15
+
## Security Advisories
16
+
17
+
Please visit the [Security Advisories](https://github.com/apache/pulsar/wiki/Security-advisories) page.
FORK_PR_BODY_URL_ENCODED=$(jq -n -r "\"This PR is for running tests for upstream PR ${PR_URL}.\n\n<!-- Before creating this PR, please ensure that the fork $FORK_REPO_URL is up to date with https://github.com/apache/pulsar -->\" | @uri")
198
+
>&2 tee -a "$GITHUB_STEP_SUMMARY"<<EOF
199
+
200
+
# Instructions for proceeding with the pull request:
201
+
202
+
apache/pulsar pull requests should be first tested in your own fork since the apache/pulsar CI based on
203
+
GitHub Actions has constrained resources and quota. GitHub Actions provides separate quota for
204
+
pull requests that are executed in a forked repository.
205
+
206
+
1. Go to ${FORK_REPO_URL} and ensure that your branch is up to date with https://github.com/apache/pulsar
207
+
Sync your fork if it's behind.
208
+
2. Open a pull request to your own fork. You can use this link to create the pull request in
209
+
your own fork:
210
+
[Create PR in fork for running tests](${FORK_REPO_URL}/compare/master...${PR_BRANCH_LABEL}?expand=1&title=${FORK_PR_TITLE_URL_ENCODED}&body=${FORK_PR_BODY_URL_ENCODED})
211
+
3. Edit the description of the pull request ${PR_URL} and add the link to the PR that you opened to your own fork
212
+
so that the reviewer can verify that tests pass in your own fork.
213
+
4. Ensure that tests pass in your own fork. Your own fork will be used to run the tests during the PR review
214
+
and any changes made during the review. You as a PR author are responsible for following up on test failures.
215
+
Please report any flaky tests as new issues at https://github.com/apache/pulsar/issues
216
+
after checking that the flaky test isn't already reported.
217
+
5. When the PR is approved, it will be possible to restart the Pulsar CI workflow within apache/pulsar
218
+
repository by adding a comment "/pulsarbot rerun-failure-checks" to the PR.
219
+
An alternative for the PR approval is to add a ready-to-test label to the PR. This can be done
220
+
by Apache Pulsar committers.
221
+
6. When tests pass on the apache/pulsar side, the PR can be merged by a Apache Pulsar Committer.
222
+
223
+
If you have any trouble you can get support in multiple ways:
224
+
* by sending email to the [dev mailing list](mailto:dev@pulsar.apache.org) ([subscribe](mailto:dev-subscribe@pulsar.apache.org))
225
+
* on the [#contributors channel on Pulsar Slack](https://apache-pulsar.slack.com/channels/contributors) ([join](https://pulsar.apache.org/community#section-discussions))
226
+
* in apache/pulsar [GitHub discussions Q&A](https://github.com/apache/pulsar/discussions/categories/q-a)
0 commit comments