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: content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md
+8-5Lines changed: 8 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,8 +64,11 @@ These labels operate cumulatively, so a self-hosted runner’s labels must match
64
64
65
65
### Routing precedence for self-hosted runners
66
66
67
-
If you use both repository-level and organization-level runners, {% data variables.product.prodname_dotcom %} follows an order of precedence when routing jobs to self-hosted runners:
68
-
69
-
1. The job's `runs-on` labels are processed. {% data variables.product.prodname_dotcom %} then attempts to locate a runner that matches the label requirements:
70
-
2. The job is sent to a repository-level runner that matches the job labels. If no repository-level runner is available (either busy, offline, or no matching labels):
71
-
3. The job is sent to an organization-level runner that matches the job labels. If no organization-level runner is available, the job request fails with an error.
67
+
When routing a job to a self-hosted runner, {% data variables.product.prodname_dotcom %} looks for a runner that matches the job's `runs-on` labels:
68
+
69
+
1. {% data variables.product.prodname_dotcom %} first searches for a runner at the repository level, then at the organization level{% if currentVersion ver_gt "enterprise-server@2.21" %}, then at the enterprise level{% endif %}.
70
+
2. The job is then sent to the first matching runner that is online and idle.
71
+
- If all matching online runners are busy, the job will queue at the level with the highest number of matching online runners.
72
+
- If all matching runners are offline, the job will queue at the level with the highest number of matching offline runners.
73
+
- If there are no matching runners at any level, the job will fail.
74
+
- If the job remains queued for more than 24 hours, the job will fail.
Copy file name to clipboardExpand all lines: content/github/site-policy/guidelines-for-legal-requests-of-user-data.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -215,6 +215,14 @@ c/o Corporation Service Company
215
215
2710 Gateway Oaks Drive, Suite 150N
216
216
Sacramento, CA 95833-3505
217
217
```
218
+
Under state and federal law, GitHub can seek reimbursement for costs associated with compliance with a valid legal demand, such as a subpoena, court order or search warrant. We only charge to recover some costs, and these reimbursements cover only a portion of the costs we actually incur to comply with legal orders.
219
+
220
+
While we do not charge in emergency situations or in other exigent circumstances, we seek reimbursement for all other legal requests in accordance with the following schedule, unless otherwise required by law:
221
+
222
+
- Initial search of up to 25 identifiers: Free
223
+
- Production of subscriber information/data for up to 5 accounts: Free
224
+
- Production of subscriber information/data for more than 5 accounts: $20 per account
225
+
- Secondary searches: $10 per search
218
226
219
227
Please make your requests as specific and narrow as possible, including the following information:
0 commit comments