Skip to content

Commit 3de34c4

Browse files
authored
Merge pull request #37640 from github/repo-sync
Repo sync
2 parents fcbda1b + f0c6820 commit 3de34c4

File tree

27 files changed

+196
-45
lines changed

27 files changed

+196
-45
lines changed
Loading
Loading
-870 Bytes
Loading
3.15 KB
Loading
1.92 KB
Loading
64 Bytes
Loading

assets/images/social-cards/issues.png

3.01 KB
Loading

content/actions/monitoring-and-troubleshooting-workflows/monitoring-workflows/adding-a-workflow-status-badge.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,19 @@ versions:
2020

2121
To add a workflow status badge to your `README.md` file, first find the URL for the status badge you would like to display. Then you can use Markdown to display the badge as an image in your `README.md` file. For more information about image markup in Markdown, see [AUTOTITLE](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#images).
2222

23+
## Using the UI
24+
25+
You can create a workflow status badge directly on the UI using the workflow file name, branch parameter, and event parameter.
26+
27+
{% data reusables.repositories.navigate-to-repo %}
28+
{% data reusables.repositories.actions-tab %}
29+
{% data reusables.repositories.navigate-to-workflow %}
30+
1. On the right side of the page, next to the "Filter workflow runs" field, click {% octicon "kebab-horizontal" aria-label="Show workflow options" %} to display a dropdown menu and click **Create status badge**.
31+
1. Optionally, select a branch if you want to display the status badge for a branch different from the default branch.
32+
1. Optionally, select the event that will trigger the workflow.
33+
1. Click **{% octicon "copy" aria-hidden="true" %} Copy status badge Markdown**.
34+
1. Copy the Markdown into your `README.md` file.
35+
2336
## Using the workflow file name
2437

2538
You can build the URL for a workflow status badge using the name of the workflow file:

content/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/exporting-membership-information-for-your-enterprise.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,8 @@ You can also use {% data variables.product.prodname_dotcom %}'s APIs to retrieve
3434

3535
Organization owners can also export membership information for an organization. For more information, see [AUTOTITLE](/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization).
3636

37+
The membership information report includes everyone associated with the enterprise, regardless of whether they consume a license. This report is useful for reviewing current enterprise membership, permissions, and roles for all individuals currently associated with the enterprise. For information about current and billable licenses, see [AUTOTITLE](/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise).
38+
3739
## Exporting a membership information report
3840

3941
You can download a CSV file containing the membership information report for your enterprise.

content/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ Before suspending site administrators, you must demote them to regular users. Se
4444
If you use certain external authentication features, you cannot manage user suspension from the site admin dashboard or command line:
4545

4646
* If LDAP Sync is enabled for {% data variables.location.product_location %}, users are automatically suspended based on the scenarios that are described in [AUTOTITLE](/admin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap#enabling-ldap-sync).
47-
* If SCIM provisioning is enabled, SCIM-provisioned users must be suspended or unsuspended through your identity provider.
47+
* If SCIM provisioning is enabled, SCIM-provisioned users must be suspended or unsuspended through your identity provider.{% ifversion scim-for-ghes-public-beta %} See [AUTOTITLE](/admin/managing-iam/provisioning-user-accounts-with-scim/provisioning-users-and-groups-with-scim-using-the-rest-api#provisioning-users-with-the-rest-api).{% endif %}
4848

4949
## Viewing suspended users in the site admin dashboard
5050

0 commit comments

Comments
 (0)