Skip to content

Commit bb51fe3

Browse files
authored
Update manage-runners.md
1 parent 5c8ba31 commit bb51fe3

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

learn-pr/github/manage-github-actions-enterprise/includes/manage-runners.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ Configuring IP allow lists helps control access to runners by restricting them t
2828

2929
| **This guide provides a detailed explanation of how** | **Self-hosted runners** |
3030
|-------------------------------------------------------|------------------------------------------------------------------------------------------|
31-
| GitHub-hosted runners use dynamic IP addresses, making it challenging to configure precise IP allowlists. | Use static or controlled IPs, allowing precise IP allowlisting or IP-based access control. |
31+
| GitHub-hosted runners use dynamic IP addresses, making it difficult to configure precise IP allowlists. | Use static or controlled IPs, allowing precise IP allowlisting or IP-based access control. |
3232
| Organizations must allow GitHub’s published IP ranges. | Can be placed behind firewalls or VPNs for added security. |
3333
| GitHub-hosted runners can be restricted using GitHub’s enterprise security settings. | Require explicit configuration to communicate with external services, enhancing security. |
3434

0 commit comments

Comments
 (0)