If you run the alternate job and it fails with a “resource not accessible by integration” error, there are two possible causes.Documentation Index
Fetch the complete documentation index at: https://docs.semgrep.dev/llms.txt
Use this file to discover all available pages before exploring further.
Your repository’s workflow permissions are set to read-only
Repository-level workflow permissions are set toread-only (default) unless they’ve previously been changed. Use of the permissions key within the workflow file does not override this setting.
To update this setting:
INFOChanging the repository’s default workflow permissions changes the permissions for all workflows in that repository. Use of the
permissions key will not override this setting, so updating it is a required step. Learn more about the permissions key at Assigning permissions to jobs, or review the example workflow-level permissions below.The workflow or job does not have the correct permissions in a private repository
In order for Semgrep findings in a private repository to appear on the GitHub Advanced Security Dashboard, you must ensure that the appropriate permissions are configured at the workflow level using thepermissions key. See the following example.
Example job configuration with permissions key
This job only requires write permissions for security-events.
