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/concepts/runners/support-for-arc.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,4 +49,4 @@ For more information about contacting {% data variables.contact.github_support %
49
49
50
50
## Working with {% data variables.contact.github_support %} for Actions Runner Controller
51
51
52
-
{% data variables.contact.github_support %} may ask questions about your Actions Runner Controller deployment and request that you collect and attach the [controller, listener](/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/troubleshooting-actions-runner-controller-errors#checking-the-logs-of-the-controller-and-runner-set-listener), and runner logs to the support ticket.
52
+
{% data variables.contact.github_support %} may ask questions about your Actions Runner Controller deployment and request that you collect and attach [controller logs, listener logs](/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/troubleshooting-actions-runner-controller-errors#checking-the-logs-of-the-controller-and-runner-set-listener), runner logs, and Helm charts (`values.yaml`) to the support ticket.
Copy file name to clipboardExpand all lines: content/billing/how-tos/pay-third-parties/cancel-marketplace-app.md
+1-3Lines changed: 1 addition & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,9 +25,7 @@ contentType: how-tos
25
25
26
26
{% ifversion fpt %}{% data reusables.marketplace.marketplace-app-page %}{% endif %}
27
27
28
-
When you cancel an app, your subscription remains active until the end of your current billing cycle. The cancellation takes effect on your next billing date. For more information, see [AUTOTITLE](/billing/managing-billing-for-github-marketplace-apps/about-billing-for-github-marketplace).
29
-
30
-
When you cancel a free trial on a paid plan, your subscription is immediately canceled and you will lose access to the app. If you don't cancel your free trial within the trial period, the payment method on file for your account will be charged for the plan you chose at the end of the trial period. For more information, see [AUTOTITLE](/billing/managing-billing-for-github-marketplace-apps/about-billing-for-github-marketplace).
28
+
**When you cancel a paid app, your access and subscription will end on your next billing date. If you cancel during a free trial, you will lose access immediately**. For more information, see [AUTOTITLE](/billing/managing-billing-for-github-marketplace-apps/about-billing-for-github-marketplace).
31
29
32
30
{% data reusables.marketplace.downgrade-marketplace-only %}
**When you cancel a sponsorship, the change will become effective on your next billing date**. {% data reusables.sponsors.no-refunds %}
16
+
17
+
## Canceling a sponsorship
18
+
19
+
{% data reusables.user-settings.access_settings %}
20
+
{% data reusables.user-settings.billing_plans %}
21
+
{% data reusables.sponsors.billing-switcher %}
22
+
1. Under "{% data variables.product.prodname_sponsors %}", next to the sponsored account, click your current tier amount, then click **Cancel sponsorship**.
23
+
1. Review the alert about canceling your sponsorship, then click **OK**.
24
+
25
+
## Canceling a scheduled sponsorship
26
+
27
+
Organizations that pay for {% data variables.product.prodname_sponsors %} by invoice can schedule the first payment for the next billing date. You can cancel the scheduled sponsorship before it becomes active.
28
+
29
+
{% data reusables.profile.access_org %}
30
+
{% data reusables.profile.org_settings %}
31
+
1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing and plans**.
32
+
1. Under "{% data variables.product.prodname_sponsors %}", in the yellow banner with the start date, click **Undo**.
33
+
1. Review the alert about undoing the activation of the sponsorship, then click **OK**.
34
+
35
+
For information about _downgrading_ a sponsorship, see [AUTOTITLE](/billing/how-tos/pay-third-parties/downgrade-sponsorship).
Copy file name to clipboardExpand all lines: content/billing/how-tos/pay-third-parties/downgrade-marketplace-app.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ contentType: how-tos
24
24
25
25
{% ifversion fpt %}{% data reusables.marketplace.marketplace-app-page %}{% endif %}
26
26
27
-
When you downgrade an app, your subscription remains active until the end of your current billing cycle. The downgrade takes effect on your next billing date. For more information, see [AUTOTITLE](/billing/managing-billing-for-github-marketplace-apps/about-billing-for-github-marketplace).
27
+
**When you downgrade an app, your subscription remains active until the end of your current billing cycle. The downgrade takes effect on your next billing date**. For more information, see [AUTOTITLE](/billing/managing-billing-for-github-marketplace-apps/about-billing-for-github-marketplace).
28
28
29
29
{% data reusables.marketplace.downgrade-marketplace-only %}
When you downgrade or cancel a sponsorship, the change will become effective on your next billing date. {% data reusables.sponsors.no-refunds %}
21
+
**When you downgrade a sponsorship, the change will become effective on your next billing date**. {% data reusables.sponsors.no-refunds %}
25
22
26
23
## Downgrading a sponsorship
27
24
@@ -31,20 +28,4 @@ When you downgrade or cancel a sponsorship, the change will become effective on
31
28
{% data reusables.sponsors.select-a-tier %}
32
29
{% data reusables.sponsors.update-sponsorship %}
33
30
34
-
## Canceling a sponsorship
35
-
36
-
{% data reusables.user-settings.access_settings %}
37
-
{% data reusables.user-settings.billing_plans %}
38
-
{% data reusables.sponsors.billing-switcher %}
39
-
1. Under "{% data variables.product.prodname_sponsors %}", next to the sponsored account, click your current tier amount, then click **Cancel sponsorship**.
40
-
1. Review the alert about canceling your sponsorship, then click **OK**.
41
-
42
-
## Canceling a scheduled sponsorship
43
-
44
-
Organizations that pay for {% data variables.product.prodname_sponsors %} by invoice can schedule the first payment for the next billing date. You can cancel the scheduled sponsorship before it becomes active.
45
-
46
-
{% data reusables.profile.access_org %}
47
-
{% data reusables.profile.org_settings %}
48
-
1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing and plans**.
49
-
1. Under "{% data variables.product.prodname_sponsors %}", in the yellow banner with the start date, click **Undo**.
50
-
1. Review the alert about undoing the activation of the sponsorship, then click **OK**.
31
+
For information about _canceling_ a sponsorship, see [AUTOTITLE](/billing/how-tos/pay-third-parties/cancel-sponsorship).
Copy file name to clipboardExpand all lines: content/billing/how-tos/pay-third-parties/end-sponsorship.md
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,15 +14,14 @@ shortTitle: End sponsorship
14
14
contentType: how-tos
15
15
---
16
16
17
-
You can set an end date to your sponsorship. The end date assigned will be the last date for which you will be charged for that sponsorship, but the sponsorship will show active for another month. For example, if October 2023 is set as the end date, the last sponsorship will be charged in October 2023, but the sponsorship will be shown as active until November 2023. For more information about setting an end date to a new sponsorship, see [AUTOTITLE](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor).
17
+
You can set an end date to your sponsorship. The end date assigned will be the last date for which you will be charged for that sponsorship, but the sponsorship will show active for another month.
18
+
19
+
For example, if July 2025 is set as the end date, the last sponsorship will be charged in July 2025, but the sponsorship will be shown as active until August 2025. For more information about setting an end date to a new sponsorship, see [AUTOTITLE](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor).
18
20
19
21
## Setting an end date for an existing sponsorship
20
22
21
23
{% data reusables.organizations.navigate-to-org %}
22
24
{% data reusables.organizations.navigate-to-sponsoring %}
23
25
1. Next to the sponsorship you want to set an end date for, click **Manage**, and then **Manage sponsorship**.
24
-
25
-

Copy file name to clipboardExpand all lines: content/billing/how-tos/pay-third-parties/upgrade-marketplace-app.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ contentType: how-tos
24
24
25
25
{% ifversion fpt %}{% data reusables.marketplace.marketplace-app-page %}{% endif %}
26
26
27
-
When you upgrade an app, your payment method is charged a prorated amount based on the time remaining until your next billing date. For more information, see [AUTOTITLE](/billing/managing-billing-for-github-marketplace-apps/about-billing-for-github-marketplace).
27
+
**When you upgrade an app, your payment method is charged a prorated amount based on the time remaining until your next billing date**. For more information, see [AUTOTITLE](/billing/managing-billing-for-github-marketplace-apps/about-billing-for-github-marketplace).
Copy file name to clipboardExpand all lines: data/reusables/actions/larger-runners-troubleshooting-linux-windows.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,4 +5,4 @@ If you notice the jobs that target your {% data variables.actions.hosted_runner
5
5
***Billing information:** You must have a valid credit card on file in order to use {% data variables.actions.hosted_runner %}s. After adding a credit card to your account, it can take up to 10 minutes to enable the use of your {% data variables.actions.hosted_runner %}s. For more information, see [AUTOTITLE](/billing/managing-your-billing/managing-your-payment-and-billing-information).
6
6
***Spending limit:** Your {% data variables.product.prodname_actions %} spending limit must be set to a value greater than zero. For more information, see [AUTOTITLE](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions).
7
7
***Fair use policy:** {% data variables.product.company_short %} has a fair use policy that begins to throttle jobs based on several factors, such as how many jobs you are running or how many jobs are running across the entirety of {% data variables.product.prodname_actions %}.
8
-
***Job queue to assign time:** Job queue to assign time refers to the time between a job request and {% data variables.product.company_short %} assigning a VM to execute the job. Standard {% data variables.product.company_short %}-hosted runners utilizing prescribed YAML workflow labels (such as `ubuntu-latest`) are always in a "warm" state. With larger runners, a warm machine may not be ready to pick up a job on first request as the pools for these machines are smaller. As a result, {% data variables.product.company_short %} may need to create a new VM, which increases the queue to assign time. Once a runner is in use, VMs are readily for subsequent workflow runs, reducing the queue to assign time for future workflow runs over the next 24 hours.
8
+
***Job queue to assign time:** Job queue to assign time refers to the time between a job request and {% data variables.product.company_short %} assigning a VM to execute the job. Standard {% data variables.product.company_short %}-hosted runners utilizing prescribed YAML workflow labels (such as `ubuntu-latest`) are always in a "warm" state. With larger runners, a warm VM may not be ready to pick up a job on first request as the pools for these machines are smaller. As a result, {% data variables.product.company_short %} may need to create a new VM, which increases the queue to assign time. Once a runner is in use, VMs are ready for subsequent workflow runs within 5 minutes. If not used again within that time, a subset of those machines remains warm, reducing the queue to assign time for future workflow runs over the next 24 hours. The higher the volume of jobs you run, the more VMs will remain in the warm pool.
0 commit comments