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
description: Learn how to automate DevOps processes by using GitHub Apps that handle repetitive tasks, enforce team policies, and maintain a tidy repository.
description: Learn how to automate DevOps processes by using GitHub Apps that handle repetitive tasks, enforce team policies, and maintain a tidy repository.
description: Learn to automate DevOps processes by using GitHub Apps that handle repetitive tasks, enforce team policies, and maintain a tidy repository.
description: Learn to automate DevOps processes by using GitHub Apps that handle repetitive tasks, enforce team policies, and maintain a tidy repository.
title: Exercise - Getting started with GitHub Apps
4
-
metadata:
5
-
title: Exercise - Getting started with GitHub Apps
6
-
description: Learn to automate DevOps processes by using GitHub Apps that handle repetitive tasks, enforce team policies, and maintain a tidy repository.
title: Exercise - Getting started with GitHub Apps
4
+
metadata:
5
+
title: Exercise - Getting started with GitHub Apps
6
+
description: Learn to automate DevOps processes by using GitHub Apps that handle repetitive tasks, enforce team policies, and maintain a tidy repository.
- content: "Which of the following scenarios is **not** a good candidate to be built as a GitHub App?"
19
-
choices:
20
-
- content: "An app that checks the spelling of pull request titles after they're created."
21
-
isCorrect: false
22
-
explanation: "This scenario is a good candidate for a GitHub app."
23
-
- content: "An app that requests a user to update the name of a pushed branch if they don't follow your team's `user/feature` branch naming convention."
24
-
isCorrect: false
25
-
explanation: "This scenario is a good candidate for a GitHub app."
26
-
- content: "An app that allows a user to approve a pull request from a custom tool."
27
-
isCorrect: true
28
-
explanation: "This scenario wouldn't be a good candidate for a GitHub app because it would need to operate on behalf of a specific user."
29
-
- content: "When should you build an OAuth App instead of a GitHub App?"
30
-
choices:
31
-
- content: "When your app needs to access the GitHub API."
32
-
isCorrect: false
33
-
explanation: "Both app models support accessing the GitHub API."
34
-
- content: "When your app needs to operate on behalf of a specific user."
35
-
isCorrect: true
36
-
explanation: "OAuth apps run as the user who authorized them. GitHub Apps run as themselves."
37
-
- content: "When your app needs to consume webhooks."
38
-
isCorrect: false
39
-
explanation: "Both app models support consuming webhooks."
40
-
- content: "Which of the following choices is **not** a benefit of using webhooks over polling?"
41
-
choices:
42
-
- content: "Webhooks have better network accessibility than polling."
43
-
isCorrect: true
44
-
explanation: "Webhooks require the publisher to connect to the subscriber to push data, which may not be practical if the subscriber is behind a firewall. However, you can mitigate this scenario through relay services like smee.io."
45
-
- content: "Webhooks use less bandwidth than polling."
46
-
isCorrect: false
47
-
explanation: "Webhooks only send data when there's data to send. Polling makes regular requests even when nothing has changed."
48
-
- content: "Webhooks offer faster delivery of new data than polling."
49
-
isCorrect: false
50
-
explanation: "Webhooks send data as soon as it becomes available. Polling can be delayed up to the polling interval length."
description: Check what you learned about GitHub Apps.
7
+
ms.date: 07/03/2025
8
+
author: a-a-ron
9
+
ms.author: aastewar
10
+
ms.topic: unit
11
+
module_assessment: true
12
+
durationInMinutes: 3
13
+
content: |
14
+
[!include[](includes/4-knowledge-check.md)]
15
+
quiz:
16
+
title: Check your knowledge
17
+
questions:
18
+
- content: "Which of the following scenarios is **not** a good candidate to be built as a GitHub App?"
19
+
choices:
20
+
- content: "An app that checks the spelling of pull request titles after they're created."
21
+
isCorrect: false
22
+
explanation: "This scenario is a good candidate for a GitHub app."
23
+
- content: "An app that requests a user to update the name of a pushed branch if they don't follow your team's `user/feature` branch naming convention."
24
+
isCorrect: false
25
+
explanation: "This scenario is a good candidate for a GitHub app."
26
+
- content: "An app that allows a user to approve a pull request from a custom tool."
27
+
isCorrect: true
28
+
explanation: "This scenario wouldn't be a good candidate for a GitHub app because it would need to operate on behalf of a specific user."
29
+
- content: "When should you build an OAuth App instead of a GitHub App?"
30
+
choices:
31
+
- content: "When your app needs to access the GitHub API."
32
+
isCorrect: false
33
+
explanation: "Both app models support accessing the GitHub API."
34
+
- content: "When your app needs to operate on behalf of a specific user."
35
+
isCorrect: true
36
+
explanation: "OAuth apps run as the user who authorized them. GitHub Apps run as themselves."
37
+
- content: "When your app needs to consume webhooks."
38
+
isCorrect: false
39
+
explanation: "Both app models support consuming webhooks."
40
+
- content: "Which of the following choices is **not** a benefit of using webhooks over polling?"
41
+
choices:
42
+
- content: "Webhooks have better network accessibility than polling."
43
+
isCorrect: true
44
+
explanation: "Webhooks require the publisher to connect to the subscriber to push data, which might not be practical if the subscriber is behind a firewall. However, you can mitigate this scenario through relay services like smee.io."
45
+
- content: "Webhooks use less bandwidth than polling."
46
+
isCorrect: false
47
+
explanation: "Webhooks only send data when there's data to send. Polling makes regular requests even when nothing is changed."
48
+
- content: "Webhooks offer faster delivery of new data than polling."
49
+
isCorrect: false
50
+
explanation: "Webhooks send data as soon as it becomes available. Polling can be delayed up to the polling interval length."
Copy file name to clipboardExpand all lines: learn-pr/github/automate-devops-github-apps/includes/1-introduction.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,10 @@
1
-
When thinking about ways to add efficiency within your GitHub workflow, you can build apps and integrations to improve and customize your workflow. By using GitHub Apps and OAuth Apps, you can help reduce the amount of time spent on manual tasks and customize your workflow to meet individual, team, and company needs. You can also share these integrations with others on GitHub Marketplace, and in return use apps and integrations that other developers have built.
1
+
When thinking about ways to add efficiency within your GitHub workflow, consider that you can build apps and integrations to improve and customize your workflow. By using GitHub Apps and OAuth Apps, you can help reduce the amount of time spent on manual tasks and customize your workflow to meet individual, team, and company needs. You can also share these integrations with others on GitHub Marketplace, and in return use apps and integrations built by other developers.
2
2
3
-
Suppose you're looking for a feature that GitHub doesn't yet support. Maybe you'd like to automate some of the more mundane tasks you deal with, such as following up with contributors who didn't label an issue they created. Or maybe you'd like to automatically close any branches or pull requests that haven't been touched in months. Whatever your need is, you're probably not alone. The good news is that GitHub Apps offer a way for you to fill the gaps and automate processes in your repository. The better news is that someone else might have already built the solution you need.
3
+
Suppose you're looking for a feature that GitHub doesn't yet support. Maybe you'd like to automate some of the more mundane tasks you deal with. For example, following up with contributors who didn't label an issue they created. Or automatically closing any branches or pull requests that remain untouched for months. Whatever your need is, you're probably not alone. The good news is that GitHub Apps offer a way for you to fill the gaps and automate processes in your repository. The better news is that the solution you need might already be built.
4
4
5
-
Optimizing the value of apps and features to manage users in your workflow can help speed up your processes while maintaining efficiency, security, and reliability. In this module, you'll learn about using these tools and their features.
5
+
Optimizing the value of apps and features to manage users in your workflow can help speed up your processes while maintaining efficiency, security, and reliability. In this module, you learn about using these tools and their features.
6
6
7
-
In this module, you'll learn how to automate DevOps processes by using GitHub Apps that handle repetitive tasks, enforce team policies, and maintain a tidy repository.
7
+
In this module, you learn how to automate DevOps processes by using GitHub Apps that handle repetitive tasks, enforce team policies, and maintain a tidy repository.
0 commit comments