diff --git a/assets/images/help/repository/actions-quickstart-job.png b/assets/images/help/repository/actions-quickstart-job.png index d083203d8d6f..3cb1eb4bc135 100644 Binary files a/assets/images/help/repository/actions-quickstart-job.png and b/assets/images/help/repository/actions-quickstart-job.png differ diff --git a/content/actions/get-started/quickstart.md b/content/actions/get-started/quickstart.md index 3fe5f816a840..6d0a6a514d94 100644 --- a/content/actions/get-started/quickstart.md +++ b/content/actions/get-started/quickstart.md @@ -98,9 +98,8 @@ If you chose to start a pull request, you can continue and create the pull reque ![Screenshot of the "Actions" page. The name of the example workflow, "GitHub Actions Demo", is highlighted by a dark orange outline.](/assets/images/help/repository/actions-quickstart-workflow-sidebar.png) 1. From the list of workflow runs, click the name of the run you want to see, in this example "USERNAME is testing out GitHub Actions." -1. In the left sidebar of the workflow run page, under **Jobs**, click the **Explore-GitHub-Actions** job. +1. In the left sidebar of the workflow run page, under **All jobs**, click the **Explore-GitHub-Actions** job. - ![Screenshot of the "Workflow run" page. In the left sidebar, the "Explore-GitHub-Actions" job is highlighted with a dark orange outline.](/assets/images/help/repository/actions-quickstart-job.png) 1. The log shows you how each of the steps was processed. Expand any of the steps to view its details. diff --git a/content/code-security/how-tos/manage-security-alerts/manage-dependabot-alerts/enable-delegated-alert-dismissal.md b/content/code-security/how-tos/manage-security-alerts/manage-dependabot-alerts/enable-delegated-alert-dismissal.md index 7cd78bfbd5d7..2d9ca61285b3 100644 --- a/content/code-security/how-tos/manage-security-alerts/manage-dependabot-alerts/enable-delegated-alert-dismissal.md +++ b/content/code-security/how-tos/manage-security-alerts/manage-dependabot-alerts/enable-delegated-alert-dismissal.md @@ -12,7 +12,10 @@ category: - Secure your dependencies --- ->[!NOTE] {% data reusables.security.delegated-alert-dismissal-capacity %} +> [!NOTE] +> {% data reusables.security.delegated-alert-dismissal-capacity %} +> +> Alert dismissal requests expire after {% ifversion dependabot-dismissal-request-expiry %}1 year{% else %}1 week{% endif %}, after which they must be resubmitted. ## Configuring delegated dismissal for a repository diff --git a/content/copilot/how-tos/administer-copilot/manage-for-organization/manage-access/grant-access.md b/content/copilot/how-tos/administer-copilot/manage-for-organization/manage-access/grant-access.md index a54bf338ec9a..c5afa9fc5e8e 100644 --- a/content/copilot/how-tos/administer-copilot/manage-for-organization/manage-access/grant-access.md +++ b/content/copilot/how-tos/administer-copilot/manage-for-organization/manage-access/grant-access.md @@ -65,13 +65,13 @@ When access is granted this way, the `copilot.cfb_seat_added` audit log event at * Click **Users and teams** to search for and add individual users or teams. - To search for a user, type their username or full name in the search bar. If you select a user who is not currently a member of your organization, they will be invited to join your organization when you click **Continue to purchase** followed by **Purchase seats**. + To search for a user, type their username or full name in the search bar. If you select a user who is neither a member nor an outside collaborator of your organization, they will be invited to join your organization when you click **Continue to purchase** followed by **Purchase seats**. When you assign a {% data variables.product.prodname_copilot_short %} seat to a user listed under **Outside collaborators** on your organization's **People** page, they will receive the seat without being invited to join the organization. * Click **Upload CSV** to add users in bulk by uploading a CSV file. To add members in bulk, click **Choose CSV to upload**, and then upload a CSV file including either the username or email address for each member you want to add, separated by a comma. The file can contain a mixture of usernames and email addresses. - > [!WARNING] When you upload a CSV file, unless you're using {% data variables.product.prodname_emus %}, {% data variables.product.prodname_copilot %} will search all users on {% data variables.product.prodname_dotcom_the_website %} for matches. If the CSV includes users who are not members of your organization, they will be invited to join your organization when you click **Continue to purchase** followed by **Purchase seats**. This warning does not apply to accounts using {% data variables.product.prodname_emus %}. + > [!WARNING] When you upload a CSV file, unless you're using {% data variables.product.prodname_emus %}, {% data variables.product.prodname_copilot %} will search all users on {% data variables.product.prodname_dotcom_the_website %} for matches. If the CSV includes users who are neither members nor outside collaborators of your organization, they will be invited to join your organization when you click **Continue to purchase** followed by **Purchase seats**. When you assign a {% data variables.product.prodname_copilot_short %} seat to a user listed under **Outside collaborators** on your organization's **People** page, they will receive the seat without being invited to join the organization. This warning does not apply to accounts using {% data variables.product.prodname_emus %}. Review the list of users generated from your CSV file. Clear the selection of any users you do not want to add. diff --git a/content/copilot/how-tos/use-copilot-agents/cloud-agent/create-automations.md b/content/copilot/how-tos/use-copilot-agents/cloud-agent/create-automations.md index c4eba9602881..aaceae606f30 100644 --- a/content/copilot/how-tos/use-copilot-agents/cloud-agent/create-automations.md +++ b/content/copilot/how-tos/use-copilot-agents/cloud-agent/create-automations.md @@ -77,6 +77,9 @@ Group members with the same ownership share persistent artifact storage, while a * **Whether activity from {% data variables.product.prodname_copilot_short %} in the cloud can trigger this {% data variables.copilot.copilot_automation %}**: From the **Can be triggered by** dropdown, pick **Anyone except {% data variables.product.prodname_copilot_short %} in the cloud** to ignore events triggered by {% data variables.product.prodname_copilot_short %}, including {% data variables.copilot.copilot_automations %}. Pick **Anyone** to listen for all events, including events triggered by {% data variables.product.prodname_copilot_short %}. * **Whether users with only read access to the repository can trigger this {% data variables.copilot.copilot_automation %}**: By default, {% data variables.copilot.copilot_automations %} ignore activity from users who don't have write access to the repository. Uncheck the **Ignore events triggered by users without write access to this repository** box to listen for these events. Depending on your repository configuration, the **Ignore events triggered by users without write access to this repository** option may be locked in an enabled state. +> [!NOTE] +> Some events created by {% data variables.product.prodname_github_apps %} cannot trigger automations. An app-authored label, assignment, closure, comment, and review events are filtered out, regardless of the app's repository permissions. Granting the app write access does not allow the event to trigger automations. + 1. In the **prompt** field, describe the task you want {% data variables.product.prodname_copilot_short %} to perform each time the {% data variables.copilot.copilot_automation %} runs. For example, `Label this issue as a bug, an enhancement, or other, based on its content.` diff --git a/content/site-policy/privacy-policies/github-subprocessors.md b/content/site-policy/privacy-policies/github-subprocessors.md index a18c9ac215da..b0c5dafc3e8d 100644 --- a/content/site-policy/privacy-policies/github-subprocessors.md +++ b/content/site-policy/privacy-policies/github-subprocessors.md @@ -18,7 +18,7 @@ The GitHub Subprocessor List identifies subprocessors authorized to subprocess c GitHub publishes the names of any new subprocessors for its online services at least 30 days in advance of the subprocessor’s authorization to perform services that may involve access to customer data or personal data. -To receive notifications of updates to this Subprocessor list, please follow the instructions provided in [AUTOTITLE](/subscriptions-and-notifications/concepts/about-notifications). +To receive notifications of updates to this Subprocessor list, please follow the instructions provided in [About notifications](/subscriptions-and-notifications/concepts/about-notifications). If you have questions about this list, please contact us at . diff --git a/data/features/dependabot-dismissal-request-expiry.yml b/data/features/dependabot-dismissal-request-expiry.yml new file mode 100644 index 000000000000..f8612e1bed34 --- /dev/null +++ b/data/features/dependabot-dismissal-request-expiry.yml @@ -0,0 +1,6 @@ +# Reference: #25178 +# Dependabot alert dismissal requests expire after 1 year instead of 1 week +versions: + fpt: '*' + ghec: '*' + ghes: '>=3.24'