Skip to content
This repository was archived by the owner on Sep 1, 2022. It is now read-only.

Commit 91d2e62

Browse files
committed
add information about pull_request.opened
1 parent cc2b872 commit 91d2e62

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

responses/07.0_add-trigger.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,10 +4,10 @@ Great! Your learner now has information about what they're expected to do in thi
44
Every step in a course will be triggered by a GitHub Event. All possible events are documented in [Events Types & Payloads on the GitHub Developer Guide](https://developer.github.com/v3/activity/events/types/).
55

66
## Step 8: Add an event
7-
Let's now find the `event` that will trigger the step. Because we want the learner to open a new Pull Request, the event we're looking for is `pull_request.opened`.
7+
Let's now find the `event` that will trigger the step. Because we want the learner to open a new Pull Request, the event we're looking for is [`pull_request`](https://developer.github.com/v3/activity/events/types/#pullrequestevent). Whenever this event occurs, information about the pull request is delivered to Learning Lab. However, if we just write `pull_request`, _any_ interaction with a pull request will cause this step to be triggered. We're specifically looking for the learner to _open a pull request_. We can filter the event to only opened pull requests by using `pull_request.opened` instead.
88

99
### :keyboard: Add an event
10-
1. Add an `event` for the first step
10+
1. Add a `pull_request.opened` event for the first step
1111
- Note: You can do this by editing the file, or accepting my suggested change
1212

1313
<hr>

0 commit comments

Comments
 (0)