From 1b17f6d9f51ed291b94ba86e09f440ae7c6434ea Mon Sep 17 00:00:00 2001 From: Laura Coursen Date: Fri, 5 Sep 2025 13:23:11 -0500 Subject: [PATCH 1/5] Clarify required permissions for updating user licenses (#57406) Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- .../how-tos/manage-plan-and-licenses/manage-user-licenses.md | 5 +++-- content/billing/tutorials/gather-insights.md | 3 +-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/content/billing/how-tos/manage-plan-and-licenses/manage-user-licenses.md b/content/billing/how-tos/manage-plan-and-licenses/manage-user-licenses.md index 9f711e976f8c..f699acf15046 100644 --- a/content/billing/how-tos/manage-plan-and-licenses/manage-user-licenses.md +++ b/content/billing/how-tos/manage-plan-and-licenses/manage-user-licenses.md @@ -17,14 +17,13 @@ topics: - Billing - Enterprise - Team -permissions: '{% data reusables.permissions.enhanced-billing-platform %}' shortTitle: Manage user licenses contentType: how-tos --- ## Organizations on {% data variables.product.prodname_team %} -If you're the owner of an organization on a {% data variables.product.prodname_team %} plan, you can add or remove user licenses to your plan through the "Licensing" page. +If you're the **owner** or **billing manager** of an organization on a {% data variables.product.prodname_team %} plan, you can add or remove user licenses to your plan through the "Licensing" page. {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} @@ -54,6 +53,8 @@ To add or remove licenses from your enterprise account: ### Self-serve customers with volume licenses +Enterprise **owners** or **billing managers** can add or remove user licenses. + 1. Navigate to your enterprise account. {% data reusables.billing.enterprise-billing-menu %} 1. In the left sidebar, click **Licensing**. diff --git a/content/billing/tutorials/gather-insights.md b/content/billing/tutorials/gather-insights.md index 56754d658a94..6f548478fa7b 100644 --- a/content/billing/tutorials/gather-insights.md +++ b/content/billing/tutorials/gather-insights.md @@ -11,7 +11,6 @@ topics: - Billing - Enterprise - Team -permissions: '{% data reusables.permissions.enhanced-billing-platform %}' product: '{% data reusables.billing.enhanced-billing-platform-product %}' shortTitle: Gather insights contentType: tutorials @@ -54,7 +53,7 @@ You can view the usage of your personal account and download the usage data for ## Viewing usage for your {% data variables.enterprise.enterprise_or_org %} -You can view the usage of your {% data variables.enterprise.enterprise_or_org %} members and download the usage data for further analysis. +{% ifversion fpt %}Organization **owners**{% elsif ghec or ghes %}Enterprise **owners**{% endif %} and **billing managers** can view the usage of your {% data variables.enterprise.enterprise_or_org %} members and download the usage data for further analysis. {% ifversion fpt %} From 8be649c05a2e05bcb1503e6c93915e5b52b0d0d3 Mon Sep 17 00:00:00 2001 From: Sharra-writes Date: Fri, 5 Sep 2025 11:35:46 -0700 Subject: [PATCH 2/5] Updating the metadata-syntax-reference intro for searchability (#57405) --- .../actions/reference/workflows-and-actions/metadata-syntax.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/actions/reference/workflows-and-actions/metadata-syntax.md b/content/actions/reference/workflows-and-actions/metadata-syntax.md index 1bcb1f7bb1c8..d07bd710d1e0 100644 --- a/content/actions/reference/workflows-and-actions/metadata-syntax.md +++ b/content/actions/reference/workflows-and-actions/metadata-syntax.md @@ -1,7 +1,7 @@ --- title: Metadata syntax reference shortTitle: Metadata syntax -intro: You can create actions to perform tasks in your repository. Actions require a metadata file that uses YAML syntax. +intro: You can create actions to perform tasks in your repository. If you’re making a custom action, it will require a metadata file that uses YAML syntax. redirect_from: - /articles/metadata-syntax-for-github-actions - /github/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions From 9f5e5a2925819b9b96b19e244fc1dceea118a79b Mon Sep 17 00:00:00 2001 From: Pallavi <96553709+pallsama@users.noreply.github.com> Date: Fri, 5 Sep 2025 11:40:58 -0700 Subject: [PATCH 3/5] Remove references to extended support (#57420) --- content/admin/all-releases.md | 2 +- .../known-issues-with-upgrades-to-your-instance.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/admin/all-releases.md b/content/admin/all-releases.md index 9af60d5df368..cecd2587ac75 100644 --- a/content/admin/all-releases.md +++ b/content/admin/all-releases.md @@ -23,7 +23,7 @@ For information about the latest release, see the [{% data variables.product.pro | Version | Candidate | Release | {% data variables.release-phases.closing_down_caps %} date | Supported | Release notes | Docs | | :- | :- | :- | :- | :-: | :- | :- | {%- for version in enterpriseServerReleases.supported %} -| {{version}} | {{enterpriseServerReleases.dates[version].displayCandidateDate}} | {{enterpriseServerReleases.dates[version].displayReleaseDate}} | Support temporarily extended until further notice | {% octicon "check" aria-label="Supported" %} | [{{version}} release notes](/enterprise-server@{{version}}/admin/release-notes) | [{{version}} docs](/enterprise-server@{{version}}) | +| {{version}} | {{enterpriseServerReleases.dates[version].displayCandidateDate}} | {{enterpriseServerReleases.dates[version].displayReleaseDate}} | {{enterpriseServerReleases.dates[version].deprecationDate}} | {% if currentDate < deprecationDate %}{% octicon "check" aria-label="Supported" %}{% else %}{% octicon "x" aria-label="Not supported" %}{% endif %} | [{{version}} release notes](/enterprise-server@{{version}}/admin/release-notes) | [{{version}} docs](/enterprise-server@{{version}}) | {%- endfor %} {%- for version in enterpriseServerReleases.deprecatedReleasesWithNewFormat %} {%- assign candidateDisplay = enterpriseServerReleases.dates[version].displayCandidateDate | default: enterpriseServerReleases.dates[version].releaseDate %} diff --git a/content/admin/upgrading-your-instance/troubleshooting-upgrades/known-issues-with-upgrades-to-your-instance.md b/content/admin/upgrading-your-instance/troubleshooting-upgrades/known-issues-with-upgrades-to-your-instance.md index 63fde0c33a7b..f45e89160c72 100644 --- a/content/admin/upgrading-your-instance/troubleshooting-upgrades/known-issues-with-upgrades-to-your-instance.md +++ b/content/admin/upgrading-your-instance/troubleshooting-upgrades/known-issues-with-upgrades-to-your-instance.md @@ -25,7 +25,7 @@ redirect_from: We have lifted the pause on upgrades to versions 3.15, 3.16, and 3.17. You can now upgrade to 3.15.12, 3.16.8, 3.17.5, or later. We do not recommend upgrading to earlier releases of 3.15, 3.16, or 3.17. As an additional step, it is recommended to check system capacity before upgrading. See [AUTOTITLE](/admin/upgrading-your-instance/preparing-to-upgrade/check-system-capacity-before-upgrading). -We are extending the support window for versions 3.14, 3.15, 3.16, and 3.17. The support window for 3.13 remains unchanged. The closing down date for each of 3.14, 3.15, 3.16, and 3.17 has been updated to "Support temporarily extended until further notice". For more information, see [AUTOTITLE](/admin/all-releases#releases-of-github-enterprise-server). +We have extended the support window for versions 3.14, 3.15, 3.16, and 3.17. The support window for 3.13 remains unchanged. The closing down date for each of 3.14, 3.15, 3.16, and 3.17 has been updated. For more information, see [AUTOTITLE](/admin/all-releases#releases-of-github-enterprise-server). We will continue to release patches for 3.14, 3.15, 3.16, and 3.17 throughout this extended support window. From 9322bdf29fa7853ef58773ebb2da08fb3aaeba77 Mon Sep 17 00:00:00 2001 From: Sam Browning <106113886+sabrowning1@users.noreply.github.com> Date: Fri, 5 Sep 2025 15:06:25 -0400 Subject: [PATCH 4/5] Fix broken link (#57422) --- content/actions/reference/workflows-and-actions/expressions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/actions/reference/workflows-and-actions/expressions.md b/content/actions/reference/workflows-and-actions/expressions.md index 9223f4be197d..5efa6184856e 100644 --- a/content/actions/reference/workflows-and-actions/expressions.md +++ b/content/actions/reference/workflows-and-actions/expressions.md @@ -278,7 +278,7 @@ Creates a hash for all `.rb` files in the `lib` directory at root level, includi You can use the following status check functions as expressions in `if` conditionals. A default status check of `success()` is applied unless you include one of these functions. For more information about `if` conditionals, see [AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idif) and [AUTOTITLE](/actions/creating-actions/metadata-syntax-for-github-actions#runsstepsif). -Outside `if` conditionals, you can use `job.status` to access the job status. For more information, see [AUTOTITLE](actions/reference/contexts-reference#job-context). +Outside `if` conditionals, you can use `job.status` to access the job status. For more information, see [AUTOTITLE](/actions/reference/contexts-reference#job-context). ### success From 3e6766dfbbadeeb44f51cae17e1ea1f7cad972a5 Mon Sep 17 00:00:00 2001 From: Laura Coursen Date: Fri, 5 Sep 2025 15:54:09 -0500 Subject: [PATCH 5/5] Clarify the 5-repository limit for scheduled reminders (#57408) --- data/reusables/reminders/scheduled-reminders-limitations.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/data/reusables/reminders/scheduled-reminders-limitations.md b/data/reusables/reminders/scheduled-reminders-limitations.md index 9a756ed7f2b3..36c219a1a25e 100644 --- a/data/reusables/reminders/scheduled-reminders-limitations.md +++ b/data/reusables/reminders/scheduled-reminders-limitations.md @@ -1,4 +1,6 @@ -Reminders will only be triggered for up to five repositories per scheduled reminder. Users can either select up to five specific repositories or allow the system to automatically choose the five repositories with the oldest average pull request age. For each repository, up to 20 of the oldest pull requests will be shown. +Each reminder is only triggered for up to **five** repositories. Users can either select up to five specific repositories, or allow the system to automatically choose the five repositories with the oldest average pull request age. For each repository, up to 20 of the oldest pull requests will be shown. + +This limit is **per reminder configuration** and **per repository owner**. If you want reminders for more than five repositories per owner, you can configure additional reminders. > [!NOTE] > Reminders are not sent when changes are merged from upstream into a fork.