Skip to content

Commit 42d959c

Browse files
committed
Improve readme
1 parent 2869b49 commit 42d959c

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

.github/workflows/README.md

+5-2
Original file line numberDiff line numberDiff line change
@@ -2,5 +2,8 @@
22

33
General guidance:
44

5-
- Please make sure to include the @dotnet/runtime-infrastructure group as a reviewer of your PRs.
6-
- Do not use the `pull_request` event. Use `pull_request_target` instead, as documented in [Workflows in forked repositories](https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#workflows-in-forked-repositories) and [pull_request_target](https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#pull_request_target).
5+
Please make sure to include the @dotnet/runtime-infrastructure group as a reviewer of your PRs.
6+
7+
For workflows that are triggered by pull requests, refer to GitHub's documentation for the pull_request and pull_request_target events. The pull_request_target event is the more common use case in this repository as it runs the workflow in the context of the target branch instead of in the context of the pull request's fork or branch. However, workflows that need to consume the contents of the pull request need to use the pull_request event. There are security considerations with each of the events though.
8+
9+
Refer to GitHub's Workflows in forked repositories and pull_request_target documentation for more information.

0 commit comments

Comments
 (0)