Skip to content

Commit 8dd7054

Browse files
Merge branch 'main' into patch-1
2 parents ced67b3 + 30a5fac commit 8dd7054

File tree

20 files changed

+64
-25
lines changed

20 files changed

+64
-25
lines changed

content/actions/how-tos/index.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,4 +18,6 @@ children:
1818
- /troubleshoot-workflows
1919
- /administer
2020
- /get-support
21+
redirect_from:
22+
- /actions/monitoring-and-troubleshooting-workflows
2123
---

content/actions/how-tos/manage-runners/github-hosted-runners/use-github-hosted-runners.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,7 @@ versions:
88
ghec: '*'
99
redirect_from:
1010
- /actions/how-tos/using-github-hosted-runners/using-github-hosted-runners
11+
- /actions/using-github-hosted-runners/using-github-hosted-runners
1112
---
1213

1314
{% ifversion ghes %}

content/actions/how-tos/manage-workflow-runs/approve-runs-from-forks.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,7 @@ redirect_from:
1313
- /actions/how-tos/managing-workflow-runs-and-deployments/managing-workflow-runs/approving-workflow-runs-from-public-forks
1414
- /actions/how-tos/managing-workflow-runs-and-deployments/managing-workflow-runs/approving-workflow-runs-from-forks
1515
- /actions/managing-workflow-runs/approving-workflow-runs-from-private-forks
16+
- /actions/managing-workflow-runs-and-deployments/managing-workflow-runs/approving-workflow-runs-from-private-forks
1617
---
1718

1819
Workflow runs triggered by a contributor's pull request from a fork may require manual approval from a maintainer with write access. You can configure workflow approval requirements for a [repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks), [organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#configuring-required-approval-for-workflows-from-public-forks), or [enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-your-enterprise).

content/actions/how-tos/monitor-workflows/index.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,5 +17,6 @@ redirect_from:
1717
- /actions/concepts/workflows-and-actions/about-monitoring-workflows
1818
- /actions/how-tos/monitoring-and-troubleshooting-workflows
1919
- /actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting
20+
- /actions/monitoring-and-troubleshooting-workflows/monitoring-workflows/about-monitoring-workflows
2021
---
2122

content/actions/how-tos/reuse-automations/share-with-your-organization.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,7 @@ redirect_from:
1111
- /actions/creating-actions/sharing-actions-and-workflows-with-your-organization
1212
- /actions/sharing-automations/sharing-actions-and-workflows-with-your-organization
1313
- /actions/how-tos/sharing-automations/sharing-actions-and-workflows-with-your-organization
14+
- /actions/administering-github-actions/sharing-workflows-secrets-and-runners-with-your-organization
1415
---
1516

1617
> [!WARNING]

content/actions/how-tos/troubleshoot-workflows.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,8 @@ redirect_from:
1111
- /actions/how-tos/monitoring-and-troubleshooting-workflows/troubleshooting-workflows/using-copilot-to-troubleshoot-workflows
1212
- /actions/how-tos/monitoring-and-troubleshooting-workflows/troubleshooting-workflows
1313
- /actions/how-tos/troubleshooting-workflows
14+
- /actions/monitoring-and-troubleshooting-workflows/troubleshooting-workflows/using-copilot-to-troubleshoot-workflows
15+
- /actions/monitoring-and-troubleshooting-workflows/troubleshooting-workflows
1416
---
1517

1618
{% data reusables.actions.enterprise-github-hosted-runners %}

content/actions/tutorials/index.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,4 +20,8 @@ children:
2020
redirect_from:
2121
- /actions/guides
2222
- /actions/how-tos/use-cases-and-examples
23+
- /actions/use-cases-and-examples/project-management/using-github-actions-for-project-management
24+
- /actions/use-cases-and-examples/project-management/moving-assigned-issues-on-project-boards
25+
- /actions/use-cases-and-examples/project-management/removing-a-label-when-a-card-is-added-to-a-project-board-column
26+
- /actions/use-cases-and-examples
2327
---

content/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/roles-in-an-enterprise.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -109,3 +109,17 @@ Enterprise members:
109109
You may need to update your IdP application to use guest collaborators. See [AUTOTITLE](/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/enabling-guest-collaborators).
110110

111111
{% endif %}
112+
113+
## Custom organization roles
114+
115+
With {% data variables.product.prodname_ghe_cloud %} and starting from {% data variables.product.prodname_ghe_server %} 3.19, enterprise owners can create custom organization roles for use in all of the enterprise's organizations. This allows centralized management of common roles such as "Developer" or "SRE team". Only enterprise owners can create or edit these roles, and any organization owner or user with the "Manage organization roles" permission can assign them in an organization.
116+
117+
When creating an organization role, enterprise owners can use the same organization and repository permissions and base roles as organization owners—there is no difference in how these roles function or what they can allow.
118+
119+
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %}
120+
1. Select the "Organization Roles" section in the left-hand menu.
121+
1. Create a new role using the "Create custom role" button, or edit an existing role using the ellipsis menu (...).
122+
123+
See [AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-organization-roles) for more information about creating and assigning custom organization roles.
124+
125+
At this time, up to 20 custom organization roles can be created by the enterprise. This limit is only for the enterprise - each organization can also create up to 20 custom organization roles.

content/admin/managing-iam/using-ldap-for-enterprise-iam/using-ldap.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -220,3 +220,5 @@ Log events for LDAP appear in systemd journal logs on {% data variables.location
220220
## Limitations for LDAP on {% data variables.product.prodname_ghe_server %}
221221

222222
The {% data variables.product.prodname_ghe_server %} LDAP authentication timeout setting is 10 seconds. This means that all LDAP queries required for user authentication and group membership queries (when Administrators and Restricted User Groups are configured in the management console) must successfully complete within 10 seconds for an LDAP user who is logging into {% data variables.product.prodname_ghe_server %}. {% data variables.product.prodname_ghe_server %} does not currently support extending this 10 second LDAP authentication timeout as this can have a negative impact on other services on the appliance and lead to poor performance or unexpected outages. We recommend limiting the network latency between {% data variables.product.prodname_ghe_server %} and LDAP server(s) to help prevent authentication timeouts.
223+
224+
{% data variables.product.prodname_ghe_server %} does not support user LDAP DNs with special characters. If there is an LDAP user with a special character in their LDAP DN, {% data variables.product.prodname_ghe_server %} may not be able to accurately determine the group membership of a user who is authenticating or being synced by LDAP Sync.

content/admin/managing-iam/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -53,9 +53,9 @@ For more information, see [AUTOTITLE](/organizations/managing-saml-single-sign-o
5353

5454
{% elsif ghes %}
5555

56-
SAML SSO allows you to centrally control and secure access to {% data variables.location.product_location %} from your SAML IdP. When an unauthenticated user visits {% data variables.location.product_location %} in a browser, {% data variables.product.github %} will redirect the user to your SAML IdP to authenticate. After the user successfully authenticates with an account on the IdP, the IdP redirects the user back to {% data variables.location.product_location %}. {% data variables.product.github %} validates the response from your IdP, then grants access to the user.
56+
SAML SSO allows you to centrally control and secure access to {% data variables.location.product_location %} from your SAML IdP.
5757

58-
After a user successfully authenticates on your IdP, the user's SAML session for {% data variables.location.product_location %} is active in the browser for 24 hours. After 24 hours, the user must authenticate again with your IdP.
58+
If an unauthenticated user attempts to sign in to {% data variables.location.product_location %} and you have disabled [built-in authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider), {% data variables.product.github %} redirects the user to your SAML IdP for authentication. After the user successfully authenticates with an account on the IdP, the IdP redirects the user back to {% data variables.location.product_location %}. {% data variables.product.github %} validates the response from your IdP, then grants access to the user. The user's SAML session is active in the browser for 24 hours. After that, the user must authenticate again with your IdP.
5959

6060
{% data reusables.saml.saml-ghes-account-revocation %}
6161

0 commit comments

Comments
 (0)