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: Learning-notes/Readme.md
+17Lines changed: 17 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -291,3 +291,20 @@ runs-on: self-hosted
291
291
292
292
If you specify an array of strings or variables, your workflow will execute on any runner that matches all of the specified runs-on values.
293
293
294
+
#### Self-Hosted Runner
295
+
Self-hosted runners can be:
296
+
297
+
- Physical
298
+
- Virtual
299
+
- In a container
300
+
- On-premises
301
+
- In a cloud
302
+
303
+
You can add self-hosted runners at various levels in the management hierarchy:
304
+
305
+
- Repository-level runners are dedicated to a single repository.
306
+
- Organization-level runners can process jobs for multiple repositories in an organization.
307
+
- Enterprise-level runners can be assigned to multiple organizations in an enterprise account.
308
+
309
+
To set up self-hosted, you need to add a runner and install the **GitHub Actions Runner** to connect the external compute to the self-hosted runner.
310
+
After installing the GitHub Actions Runner, ensure **port 443** is open in your outbound rules to allow secure communication between the runner and GitHub.
0 commit comments