diff --git a/content/admin/managing-code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise.md b/content/admin/managing-code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise.md index 88535a391ed1..c7db586c91b6 100644 --- a/content/admin/managing-code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise.md +++ b/content/admin/managing-code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise.md @@ -32,6 +32,14 @@ To manage individual {% data variables.product.prodname_GH_advanced_security %} {% endif %} +{% ifversion ghec %} + +{% data variables.product.prodname_security_configurations_caps %} simplify the rollout of {% data variables.product.company_short %} security products at scale by helping you define collections of security settings and apply them across your enterprise. For more information, see [AUTOTITLE](/admin/managing-code-security/securing-your-enterprise/about-security-configurations). + +{% data reusables.security-configurations.overview %} + +{% endif %} + {% data reusables.secret-scanning.secret-scanning-enterprise-level-api %} {% ifversion ghes %}For information about buying a license for {% data variables.product.prodname_GH_advanced_security %}, see [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security).{% elsif ghec %}For information about buying a license for {% data variables.product.prodname_GH_advanced_security %}, see [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-advanced-security/signing-up-for-github-advanced-security).{% endif %} @@ -42,23 +50,26 @@ When you enable one or more security and analysis features for existing reposito {% data reusables.security.security-and-analysis-features-enable-read-only %} +{% ifversion ghes %} + ## Managing {% data variables.product.prodname_advanced_security %} features {% data reusables.advanced-security.note-org-enable-uses-seats %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} - -1. In the left sidebar, click {% ifversion code-security-wording-only %}**Code security**{% else %}**Code security and analysis**{% endif %}. +1. In the left sidebar, click **Code security and analysis**. 1. Optionally, enable or disable a feature for all existing repositories. - * To the right of the feature, click **Disable all** or **Enable all**. {% ifversion ghes or ghec %}If the control for "{% data variables.product.prodname_GH_advanced_security %}" is disabled, you have no available licenses for {% data variables.product.prodname_GH_advanced_security %}.{% endif %} + * To the right of the feature, click **Disable all** or **Enable all**. If the control for "{% data variables.product.prodname_GH_advanced_security %}" is disabled, you have no available licenses for {% data variables.product.prodname_GH_advanced_security %}. * To confirm the change, click the **Enable/Disable all** or **Enable/Disable for eligible repositories** button in the dialog that is displayed. -1. Optionally, to enable or disable a feature automatically when new private and internal repositories{% ifversion secret-scanning-user-owned-repos %}, user namespace repositories {% ifversion ghec %}belonging to {% data variables.product.prodname_emus %}{% endif %}{% endif %}, or public repositories and repositories with {% data variables.product.prodname_GH_advanced_security %} enabled are created, select the checkbox below the feature. -{% ifversion secret-scanning-custom-link-on-block %} +1. Optionally, to enable or disable a feature automatically when new private and internal repositories{% ifversion secret-scanning-user-owned-repos %}, user namespace repositories{% endif %}, or public repositories and repositories with {% data variables.product.prodname_GH_advanced_security %} enabled are created, select the checkbox below the feature.{% ifversion org-npp-enablement-security-configurations %} +1. Optionally, to enable the scanning of non-provider patterns, to the right of "Scan for non-provider patterns", click **Enable all**. To learn more about scanning for non-provider patterns, see [AUTOTITLE](/code-security/secret-scanning/introduction/supported-secret-scanning-patterns#non-provider-patterns) and [AUTOTITLE](/code-security/secret-scanning/managing-alerts-from-secret-scanning/viewing-alerts).{% endif %} 1. Optionally, to include a resource link in the message that members will see when they attempt to push a secret, select **Add a resource link in the CLI and web UI when a commit is blocked**, then type a URL, and click **Save link**. > [!NOTE] > When a custom link is configured for an organization, the organization-level value overrides the custom link set for the enterprise. See [AUTOTITLE](/code-security/secret-scanning/protecting-pushes-with-secret-scanning). - ![Screenshot of "Push protection" settings. The checkbox and text field used for enabling a custom link are outlined.](/assets/images/help/organizations/secret-scanning-custom-link.png){% endif %} + ![Screenshot of "Push protection" settings. The checkbox and text field used for enabling a custom link are outlined.](/assets/images/help/organizations/secret-scanning-custom-link.png) + +{% endif %} diff --git a/content/admin/managing-code-security/securing-your-enterprise/about-security-configurations.md b/content/admin/managing-code-security/securing-your-enterprise/about-security-configurations.md index 6d380faeb990..337fbbaaa12b 100644 --- a/content/admin/managing-code-security/securing-your-enterprise/about-security-configurations.md +++ b/content/admin/managing-code-security/securing-your-enterprise/about-security-configurations.md @@ -15,13 +15,7 @@ topics: {% data variables.product.prodname_security_configurations_caps %} simplify the rollout of {% data variables.product.company_short %} security products at scale by helping you define collections of security settings and apply them across your enterprise. -{% ifversion security-configurations-cloud %} - -We recommend securing your enterprise with the {% data variables.product.prodname_github_security_configuration %}, then evaluating the security findings on your repositories before configuring {% data variables.product.prodname_custom_security_configurations %}. For more information, see [AUTOTITLE](/admin/managing-code-security/securing-your-enterprise/applying-the-github-recommended-security-configuration-to-your-enterprise). - -{% endif %} - -With {% data variables.product.prodname_custom_security_configurations %}, you can create collections of enablement settings for {% data variables.product.company_short %}'s security products to meet the specific security needs of your enterprise. For example, you can create a different {% data variables.product.prodname_custom_security_configuration %} for each organization or group of similar organizations to reflect their different levels of security requirements and compliance obligations. For more information, see [AUTOTITLE](/admin/managing-code-security/securing-your-enterprise/creating-a-custom-security-configuration-for-your-enterprise). +{% data reusables.security-configurations.overview %} {% ifversion security-configurations-ghes-only %} diff --git a/content/admin/overview/about-github-for-enterprises.md b/content/admin/overview/about-github-for-enterprises.md index ecce51b970f9..d398241cdd7c 100644 --- a/content/admin/overview/about-github-for-enterprises.md +++ b/content/admin/overview/about-github-for-enterprises.md @@ -86,7 +86,7 @@ When businesses adopt {% data variables.product.prodname_enterprise %}, their re 1. Learn more about {% data variables.product.prodname_enterprise %}. * [AUTOTITLE](/enterprise-cloud@latest/admin/overview/about-github-enterprise-cloud){% ifversion not ghec %} in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %} - * [AUTOTITLE]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/overview/about-github-enterprise-server){% ifversion not ghes %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% else %}.{% endif %} + * [AUTOTITLE]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/overview/about-github-enterprise-server){% ifversion not ghes %} in the {% data variables.product.prodname_ghe_server %} documentation.{% else %}.{% endif %} 1. Set up a trial. * [AUTOTITLE](/admin/overview/setting-up-a-trial-of-github-enterprise-cloud) diff --git a/content/code-security/codeql-cli/codeql-cli-manual/test-extract.md b/content/code-security/codeql-cli/codeql-cli-manual/test-extract.md index d39990869d22..5faefca89bcd 100644 --- a/content/code-security/codeql-cli/codeql-cli-manual/test-extract.md +++ b/content/code-security/codeql-cli/codeql-cli-manual/test-extract.md @@ -24,7 +24,7 @@ redirect_from: ## Synopsis ```shell copy -codeql test extract ... -- +codeql test extract [--source-root=] ... -- ``` ## Description @@ -39,7 +39,7 @@ execute test queries against. ### Primary Options -#### `` +#### `` \[Mandatory] The path to the test directory. @@ -49,6 +49,11 @@ Override the location of the database being created. By default it will be a subdirectory whose name is derived from the name of the test directory itself with '.testproj' appended. +#### `-s, --source-root=` + +\[Advanced] The root source code directory, if different from the test +directory. + #### `--search-path=[:...]` A list of directories under which extractor packs may be found. The diff --git a/content/copilot/rolling-out-github-copilot-at-scale/driving-copilot-adoption-in-your-company.md b/content/copilot/rolling-out-github-copilot-at-scale/driving-copilot-adoption-in-your-company.md index 7a0093269063..5b73593b5ad2 100644 --- a/content/copilot/rolling-out-github-copilot-at-scale/driving-copilot-adoption-in-your-company.md +++ b/content/copilot/rolling-out-github-copilot-at-scale/driving-copilot-adoption-in-your-company.md @@ -85,6 +85,6 @@ If your organization has specific {% data variables.product.prodname_copilot_sho Once you have implemented your {% data variables.product.prodname_copilot_short %} enablement process, you should regularly review and optimize it to ensure it continues to meet your organization's needs. Some ways you can do this are: * Monitoring usage data to identify trends and patterns. See [AUTOTITLE](/copilot/rolling-out-github-copilot-at-scale/analyzing-usage-over-time-with-the-copilot-metrics-api). -* Following up with users who haven't been using their assigned license. You can use the API to see the latest activity date for each assigned seat. See [AUTOTITLE](/rest/copilot/copilot-user-management#list-all-copilot-seat-assignments-for-an-organization). -* Gathering feedback from teams to understand what is working well and what could be improved -* Reviewing {% data variables.product.prodname_discussions %} and other communication channels to identify common issues and questions +* Following up with users who haven't been using their assigned license. You can use the API to see the latest activity date for each assigned seat. See [AUTOTITLE](/copilot/rolling-out-github-copilot-at-scale/reminding-inactive-users). +* Gathering feedback from teams to understand what is working well and what could be improved. +* Reviewing {% data variables.product.prodname_discussions %} and other communication channels to identify common issues and questions. diff --git a/content/copilot/rolling-out-github-copilot-at-scale/index.md b/content/copilot/rolling-out-github-copilot-at-scale/index.md index c00a2a386dbb..9ca0c32b31e1 100644 --- a/content/copilot/rolling-out-github-copilot-at-scale/index.md +++ b/content/copilot/rolling-out-github-copilot-at-scale/index.md @@ -9,4 +9,5 @@ topics: children: - /driving-copilot-adoption-in-your-company - /analyzing-usage-over-time-with-the-copilot-metrics-api + - /reminding-inactive-users --- diff --git a/content/copilot/rolling-out-github-copilot-at-scale/reminding-inactive-users.md b/content/copilot/rolling-out-github-copilot-at-scale/reminding-inactive-users.md new file mode 100644 index 000000000000..0eb793767ae7 --- /dev/null +++ b/content/copilot/rolling-out-github-copilot-at-scale/reminding-inactive-users.md @@ -0,0 +1,148 @@ +--- +title: Reminding inactive users to use their GitHub Copilot license +shortTitle: Remind inactive users +intro: 'Use the {% data variables.product.github %} API to identify inactive users and help them get started.' +versions: + feature: copilot +permissions: Organization owners and billing managers +product: '{% data variables.product.prodname_copilot_for_business %} or {% data variables.product.prodname_copilot_enterprise %}' +topics: + - Copilot +allowTitleToDifferFromFilename: true +layout: inline +--- + +When you're rolling out {% data variables.product.prodname_copilot %} in a business, it's important to keep track of which users are using their {% data variables.product.prodname_copilot_short %} license, so you can respond effectively by reassigning unused licenses or helping people to get started with {% data variables.product.prodname_copilot_short %}. + +You can use the [List all Copilot seat assignments for an organization](/rest/copilot/copilot-user-management#list-all-copilot-seat-assignments-for-an-organization) API endpoint to find the last activity date for each user who is assigned a license in an organization. Then, you can respond automatically by filtering for users who haven't used their license for a certain amount of time and sending a reminder to those users. + +## Writing the reminder message + +Your reminder to inactive users should help users to get past common adoption blockers for {% data variables.product.prodname_copilot_short %}. We recommend identifying specific blockers for your company by running surveys or interviewing developers. + +For example, the message could include information and links to help users: + +* Install {% data variables.product.prodname_copilot_short %} in their environment. +* Set up {% data variables.product.prodname_copilot_short %} to work with your company's proxy or firewall. +* Get the most out of {% data variables.product.prodname_copilot_short %} in their day-to-day work. + +You should also clearly communicate any further action you will take if the license continues to go unused, such as revoking the user's license. + +### Example reminder + +In the next section, we'll use this message in an automation that creates an issue assigned to each inactive user. + +> We noticed you haven't used your assigned license for {% data variables.product.prodname_copilot %} in 30 days. Here are some resources that might help you get started: +> +> * If you haven't yet set up {% data variables.product.prodname_copilot_short %} in your environment, see [AUTOTITLE](/copilot/setting-up-github-copilot/setting-up-github-copilot-for-yourself) or [AUTOTITLE](/copilot/troubleshooting-github-copilot/troubleshooting-common-issues-with-github-copilot). +> * For best practices and advice on getting started, see [AUTOTITLE](/copilot/using-github-copilot/best-practices-for-using-github-copilot) or [AUTOTITLE](/copilot/using-github-copilot/prompt-engineering-for-github-copilot). +> * For examples related to specific tasks, see [AUTOTITLE](/copilot/example-prompts-for-github-copilot-chat). +> +> If you no longer need access to {% data variables.product.prodname_copilot_short %}, please let us know in this issue. If your license remains inactive for a further 30 days, we'll revoke it to free up access for another user. + +#### Example reminder in Markdown + + + +``` markdown copy +We noticed you haven't used your assigned license for {% data variables.product.prodname_copilot %} in 30 days. Here are some resources that might help you get started: + +* If you haven't yet set up Copilot in your environment, see [Setting up GitHub Copilot for yourself](https://docs.github.com/en/copilot/setting-up-github-copilot/setting-up-github-copilot-for-yourself) or [Troubleshooting common issues with GitHub Copilot](https://docs.github.com/en/copilot/troubleshooting-github-copilot/troubleshooting-common-issues-with-github-copilot). +* For best practices and advice on getting started, see [Best practices for using GitHub Copilot](https://docs.github.com/en/copilot/using-github-copilot/best-practices-for-using-github-copilot) or [Prompt engineering for GitHub Copilot](https://docs.github.com/en/copilot/using-github-copilot/prompt-engineering-for-github-copilot). +* For examples related to specific tasks, see [Copilot Chat Cookbook](https://docs.github.com/en/copilot/example-prompts-for-github-copilot-chat). + +If you no longer need access to {% data variables.product.prodname_copilot_short %}, please let us know in this issue. If your license remains inactive for a further 30 days, we'll revoke it to free up access for another user. +``` + + + +## Automating the reminder with {% data variables.product.prodname_actions %} + +The following example workflow uses the API to identify users in an organization who haven't used their license for 30 days, then creates an issue assigned to each user. This is a simple example that you can adapt to meet your needs. + +To use this workflow: + +1. Create a label in the repository where reminder issues will be created. Call the label `copilot-reminder`. We'll use this label to check whether a reminder issue is already open for each inactive user. + + To create a label, see [AUTOTITLE](/issues/using-labels-and-milestones-to-track-work/managing-labels#creating-a-label). +1. Save your reminder message, such as the one provided in [Example reminder in Markdown](#example-reminder-in-markdown), as an {% data variables.product.prodname_actions %} variable in your repository or organization. Call the variable `COPILOT_REMINDER_MESSAGE`. + + To create a variable, see [AUTOTITLE](/actions/writing-workflows/choosing-what-your-workflow-does/store-information-in-variables#creating-configuration-variables-for-a-repository). +1. Create a {% data variables.product.pat_generic %} with permission to call the [List all Copilot seat assignments for an organization](/rest/copilot/copilot-user-management#list-all-copilot-seat-assignments-for-an-organization) API endpoint. For example, create a fine-grained token with the following details: + * **Resource owner**: The organization where you're looking for inactive users. + * **Organization permissions**: {% data variables.product.prodname_copilot_for_business %} (read-only). + + To create a token, see [AUTOTITLE](/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#creating-a-fine-grained-personal-access-token). +1. Save the access token as a {% data variables.product.prodname_actions %} secret in your repository or organization. Call the secret `COPILOT_LICENSE_READ`. + + To create a secret, see [AUTOTITLE](/actions/security-for-github-actions/security-guides/using-secrets-in-github-actions#creating-secrets-for-a-repository). +1. Using the example below, create the workflow in the repository where you want the reminder issues to be created. + + If you're new to {% data variables.product.prodname_actions %}, see [AUTOTITLE](/actions/writing-workflows/quickstart). +1. In the workflow, replace the `ORG/REPO` placeholders in the `gh` commands with the name of the repository where you want the reminder issues to be created. For example: `octo-org/octo-repo`. + +### Example workflow + +>[!NOTE] This example assumes you assign licenses through an organization. If you use a dedicated enterprise account for {% data variables.product.prodname_copilot_business_short %}, you will need to use different API endpoints. See [AUTOTITLE](/admin/copilot-business-only/setting-up-a-dedicated-enterprise-for-copilot-business-personal-accounts#automate-license-management). + + + +``` yaml annotate +# Name your workflow +name: Remind inactive users about Copilot license + +# Run the workflow every day at 8am UTC +on: + schedule: + - cron: '0 8 * * *' + +jobs: + context-log: + runs-on: ubuntu-latest + steps: + - name: Check Copilot Last Activity + id: check-last-activity + run: | + # Call the user management API + RESPONSE=$(gh api \ + -H "Accept: application/vnd.github+json" \ + -H "X-GitHub-Api-Version: 2022-11-28" \ + -H "Authorization: Bearer {% raw %}${{ secrets.COPILOT_LICENSE_READ }}{% endraw %}" \ + /orgs/$ORGANIZATION_VAR/copilot/billing/seats) + echo "Raw Response from gh api:" + echo "$RESPONSE" + + # Parse and check each user's `last_activity_at` + echo "$RESPONSE" | jq -c '.seats[]' | while read -r seat; do + LOGIN=$(echo "$seat" | jq -r '.assignee.login') + LAST_ACTIVITY=$(echo "$seat" | jq -r '.last_activity_at') + + # Replace ORG/REPO with the repository name + EXISTING_ISSUES=$(gh issue list --repo ORG/REPO --assignee $LOGIN --label 'copilot-reminder' --json id) + + # Convert dates to seconds since epoch for comparison + LAST_ACTIVITY_DATE=$(date -d "$LAST_ACTIVITY" +%s) + THIRTY_DAYS_AGO=$(date -d "30 days ago" +%s) + + # Create issues for inactive users who don't have an existing open issue + if [ "$LAST_ACTIVITY_DATE" -lt "$THIRTY_DAYS_AGO" ] && [ "$EXISTING_ISSUES" = "[]" ]; then + echo "User $LOGIN has not been active in the last 30 days. Last activity: $LAST_ACTIVITY" + + # Replace ORG/REPO with the repository name + NEW_ISSUE_URL="$(gh issue create --title "Reminder about your GitHub Copilot license" --body "{% raw %}${{ vars.COPILOT_REMINDER_MESSAGE }}{% endraw %}" --repo ORG/REPO --assignee $LOGIN --label 'copilot-reminder')" + else + echo "User $LOGIN is active or already has an assigned reminder issue. Last activity: $LAST_ACTIVITY" + fi + done + + # Set the GITHUB_TOKEN, required for the `gh issue` commands + env: + GITHUB_TOKEN: {% raw %}${{ github.token }}{% endraw %} +``` + + + +## Further reading + +* [AUTOTITLE](/copilot/rolling-out-github-copilot-at-scale/driving-copilot-adoption-in-your-company) +* [AUTOTITLE](/copilot/rolling-out-github-copilot-at-scale/analyzing-usage-over-time-with-the-copilot-metrics-api) diff --git a/data/reusables/security-configurations/overview.md b/data/reusables/security-configurations/overview.md new file mode 100644 index 000000000000..6af55e86f2e7 --- /dev/null +++ b/data/reusables/security-configurations/overview.md @@ -0,0 +1,7 @@ +{% ifversion security-configurations-cloud %} + +We recommend securing your enterprise with the {% data variables.product.prodname_github_security_configuration %}, then evaluating the security findings on your repositories before configuring {% data variables.product.prodname_custom_security_configurations %}. For more information, see [AUTOTITLE](/admin/managing-code-security/securing-your-enterprise/applying-the-github-recommended-security-configuration-to-your-enterprise). + +{% endif %} + +With {% data variables.product.prodname_custom_security_configurations %}, you can create collections of enablement settings for {% data variables.product.company_short %}'s security products to meet the specific security needs of your enterprise. For example, you can create a different {% data variables.product.prodname_custom_security_configuration %} for each organization or group of similar organizations to reflect their different levels of security requirements and compliance obligations. For more information, see [AUTOTITLE](/admin/managing-code-security/securing-your-enterprise/creating-a-custom-security-configuration-for-your-enterprise). diff --git a/data/reusables/security-configurations/view-configurations-page-enterprise.md b/data/reusables/security-configurations/view-configurations-page-enterprise.md new file mode 100644 index 000000000000..160841ed6ae0 --- /dev/null +++ b/data/reusables/security-configurations/view-configurations-page-enterprise.md @@ -0,0 +1 @@ +1. Under "Settings", select the {% ifversion ghec %}**Code security**{% else %}**Code security and analysis**{% endif %} dropdown menu. diff --git a/src/audit-logs/data/fpt/organization.json b/src/audit-logs/data/fpt/organization.json index be20ef5a994a..7273fc549f90 100644 --- a/src/audit-logs/data/fpt/organization.json +++ b/src/audit-logs/data/fpt/organization.json @@ -2399,6 +2399,16 @@ "description": "A code scanning configuration for a branch of a repository was deleted.", "docs_reference_links": "/code-security/code-scanning/managing-code-scanning-alerts/managing-code-scanning-alerts-for-your-repository#removing-stale-configurations-and-alerts-from-a-branch" }, + { + "action": "repo.code_scanning_delegated_alert_dismissal_disabled", + "description": "Prevention of direct alert dismissal for code scanning was disabled for a repository.", + "docs_reference_links": "N/A" + }, + { + "action": "repo.code_scanning_delegated_alert_dismissal_enabled", + "description": "Prevention of direct alert dismissal for code scanning was enabled for a repository.", + "docs_reference_links": "N/A" + }, { "action": "repo.codeql_disabled", "description": "Code scanning using the default setup was disabled for a repository.", diff --git a/src/audit-logs/data/ghec/enterprise.json b/src/audit-logs/data/ghec/enterprise.json index c322a5814341..3d3800be499b 100644 --- a/src/audit-logs/data/ghec/enterprise.json +++ b/src/audit-logs/data/ghec/enterprise.json @@ -364,6 +364,11 @@ "description": "The ability for enterprise members to update branch protection rules was enabled. Enterprise owners and members can update protected branches.", "docs_reference_links": "N/A" }, + { + "action": "business.proxy_security_header_disabled", + "description": "The proxy security header was disabled for an enterprise. All users on the network can now access GitHub, unless blocked by other means.", + "docs_reference_links": "N/A" + }, { "action": "business.proxy_security_header_enabled", "description": "The proxy security header was enabled for an enterprise. When the header is provided in requests, only Enterprise Managed Users matching the header will be able to access GitHub.", @@ -3179,6 +3184,16 @@ "description": "A code scanning configuration for a branch of a repository was deleted.", "docs_reference_links": "/code-security/code-scanning/managing-code-scanning-alerts/managing-code-scanning-alerts-for-your-repository#removing-stale-configurations-and-alerts-from-a-branch" }, + { + "action": "repo.code_scanning_delegated_alert_dismissal_disabled", + "description": "Prevention of direct alert dismissal for code scanning was disabled for a repository.", + "docs_reference_links": "N/A" + }, + { + "action": "repo.code_scanning_delegated_alert_dismissal_enabled", + "description": "Prevention of direct alert dismissal for code scanning was enabled for a repository.", + "docs_reference_links": "N/A" + }, { "action": "repo.codeql_disabled", "description": "Code scanning using the default setup was disabled for a repository.", diff --git a/src/audit-logs/data/ghec/organization.json b/src/audit-logs/data/ghec/organization.json index be20ef5a994a..7273fc549f90 100644 --- a/src/audit-logs/data/ghec/organization.json +++ b/src/audit-logs/data/ghec/organization.json @@ -2399,6 +2399,16 @@ "description": "A code scanning configuration for a branch of a repository was deleted.", "docs_reference_links": "/code-security/code-scanning/managing-code-scanning-alerts/managing-code-scanning-alerts-for-your-repository#removing-stale-configurations-and-alerts-from-a-branch" }, + { + "action": "repo.code_scanning_delegated_alert_dismissal_disabled", + "description": "Prevention of direct alert dismissal for code scanning was disabled for a repository.", + "docs_reference_links": "N/A" + }, + { + "action": "repo.code_scanning_delegated_alert_dismissal_enabled", + "description": "Prevention of direct alert dismissal for code scanning was enabled for a repository.", + "docs_reference_links": "N/A" + }, { "action": "repo.codeql_disabled", "description": "Code scanning using the default setup was disabled for a repository.", diff --git a/src/audit-logs/lib/config.json b/src/audit-logs/lib/config.json index 560635a37193..428a1859fdd3 100644 --- a/src/audit-logs/lib/config.json +++ b/src/audit-logs/lib/config.json @@ -3,5 +3,5 @@ "apiOnlyEvents": "This event is not available in the web interface, only via the REST API, audit log streaming, or JSON/CSV exports.", "apiRequestEvent": "This event is only available via audit log streaming." }, - "sha": "cc5c30b400bb9bfc6db55dfef4522ac840be69b0" + "sha": "3e16bd86cc7cd0434f9ee966d6fda05fbfbb00cd" } \ No newline at end of file