# OrgsUpdateRequest

## Properties

Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
**billing_email** | Option<**String**> | Billing email address. This address is not publicized. | [optional]
**company** | Option<**String**> | The company name. | [optional]
**email** | Option<**String**> | The publicly visible email address. | [optional]
**twitter_username** | Option<**String**> | The Twitter username of the company. | [optional]
**location** | Option<**String**> | The location. | [optional]
**name** | Option<**String**> | The shorthand name of the company. | [optional]
**description** | Option<**String**> | The description of the company. The maximum size is 160 characters. | [optional]
**has_organization_projects** | Option<**bool**> | Whether an organization can use organization projects. | [optional]
**has_repository_projects** | Option<**bool**> | Whether repositories that belong to the organization can use repository projects. | [optional]
**default_repository_permission** | Option<**String**> | Default permission level members have for organization repositories. | [optional][default to Read]
**members_can_create_repositories** | Option<**bool**> | Whether of non-admin organization members can create repositories. **Note:** A parameter can override this parameter. See `members_allowed_repository_creation_type` in this table for details. | [optional][default to true]
**members_can_create_internal_repositories** | Option<**bool**> | Whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation. | [optional]
**members_can_create_private_repositories** | Option<**bool**> | Whether organization members can create private repositories, which are visible to organization members with permission. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation. | [optional]
**members_can_create_public_repositories** | Option<**bool**> | Whether organization members can create public repositories, which are visible to anyone. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation. | [optional]
**members_allowed_repository_creation_type** | Option<**String**> | Specifies which types of repositories non-admin organization members can create. `private` is only available to repositories that are part of an organization on GitHub Enterprise Cloud.  **Note:** This parameter is deprecated and will be removed in the future. Its return value ignores internal repositories. Using this parameter overrides values set in `members_can_create_repositories`. See the parameter deprecation notice in the operation description for details. | [optional]
**members_can_create_pages** | Option<**bool**> | Whether organization members can create GitHub Pages sites. Existing published sites will not be impacted. | [optional][default to true]
**members_can_create_public_pages** | Option<**bool**> | Whether organization members can create public GitHub Pages sites. Existing published sites will not be impacted. | [optional][default to true]
**members_can_create_private_pages** | Option<**bool**> | Whether organization members can create private GitHub Pages sites. Existing published sites will not be impacted. | [optional][default to true]
**members_can_fork_private_repositories** | Option<**bool**> | Whether organization members can fork private organization repositories. | [optional][default to false]
**web_commit_signoff_required** | Option<**bool**> | Whether contributors to organization repositories are required to sign off on commits they make through GitHub's web interface. | [optional][default to false]
**blog** | Option<**String**> |  | [optional]
**advanced_security_enabled_for_new_repositories** | Option<**bool**> | Whether GitHub Advanced Security is automatically enabled for new repositories.  To use this parameter, you must have admin permissions for the repository or be an owner or security manager for the organization that owns the repository. For more information, see \"[Managing security managers in your organization](https://docs.github.com/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization).\"  You can check which security and analysis features are currently enabled by using a `GET /orgs/{org}` request. | [optional]
**dependabot_alerts_enabled_for_new_repositories** | Option<**bool**> | Whether Dependabot alerts is automatically enabled for new repositories.  To use this parameter, you must have admin permissions for the repository or be an owner or security manager for the organization that owns the repository. For more information, see \"[Managing security managers in your organization](https://docs.github.com/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization).\"  You can check which security and analysis features are currently enabled by using a `GET /orgs/{org}` request. | [optional]
**dependabot_security_updates_enabled_for_new_repositories** | Option<**bool**> | Whether Dependabot security updates is automatically enabled for new repositories.  To use this parameter, you must have admin permissions for the repository or be an owner or security manager for the organization that owns the repository. For more information, see \"[Managing security managers in your organization](https://docs.github.com/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization).\"  You can check which security and analysis features are currently enabled by using a `GET /orgs/{org}` request. | [optional]
**dependency_graph_enabled_for_new_repositories** | Option<**bool**> | Whether dependency graph is automatically enabled for new repositories.  To use this parameter, you must have admin permissions for the repository or be an owner or security manager for the organization that owns the repository. For more information, see \"[Managing security managers in your organization](https://docs.github.com/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization).\"  You can check which security and analysis features are currently enabled by using a `GET /orgs/{org}` request. | [optional]
**secret_scanning_enabled_for_new_repositories** | Option<**bool**> | Whether secret scanning is automatically enabled for new repositories.  To use this parameter, you must have admin permissions for the repository or be an owner or security manager for the organization that owns the repository. For more information, see \"[Managing security managers in your organization](https://docs.github.com/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization).\"  You can check which security and analysis features are currently enabled by using a `GET /orgs/{org}` request. | [optional]
**secret_scanning_push_protection_enabled_for_new_repositories** | Option<**bool**> | Whether secret scanning push protection is automatically enabled for new repositories.  To use this parameter, you must have admin permissions for the repository or be an owner or security manager for the organization that owns the repository. For more information, see \"[Managing security managers in your organization](https://docs.github.com/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization).\"  You can check which security and analysis features are currently enabled by using a `GET /orgs/{org}` request. | [optional]
**secret_scanning_push_protection_custom_link_enabled** | Option<**bool**> | Whether a custom link is shown to contributors who are blocked from pushing a secret by push protection. | [optional]
**secret_scanning_push_protection_custom_link** | Option<**String**> | If `secret_scanning_push_protection_custom_link_enabled` is true, the URL that will be displayed to contributors who are blocked from pushing a secret. | [optional]

[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)