...
Parameter | Type | Description | Required | Default | ||
|---|---|---|---|---|---|---|
includedOwners->exactNames | Array | Define a whitelist of GitHub Organizations and/or GitHub repository owners who can integrate with the WhiteSource integration. NOTE: This applies to WhiteSource for GitHub Enterprise and WhiteSource for GitHub.com only. For example:
| No | Empty | ||
allowedUserAccounts->exactNames | Array | Provide a way to limit the integration to organization accounts and block all or specific user accounts. If the “exactNames” property is empty all user accounts will be blocked. If the object is missing, no limitation on account type will be enforced. When a blocked account is trying to install the integration it will be automatically uninstalled. NOTE: Only valid for the GitHub Enterprise integration.
| No | Null |
Manually Triggering Repository
NOTE: Relevant only for WhiteSource for GitHub Enterprise Integration and WhiteSource for GitHub.com Integration.
This feature enables users to manually trigger scans for specific repositories.
In order to trigger the manual scans, a file called scan.json needs to be pushed to the whitesource-config repo. The scan.json file contains a list of repositories to scan:
| Code Block |
|---|
{
"repositories": [
{
"fullName": "orgName1/repoName1",
"branchName": "main"
}
]
} |
The repository list is limited to 10. If there are more than 10, no repositories will be scanned, and a check run saying so will be created.
If a branch name is not specified - the default branch will be scanned.
For each repository in the list, a scan will be triggered (in the latest commit of the specified branch), including the creation of the security check run.
Migrating Existing Repositories to the Global Configuration
...