95e6f3d3ab
* add 3.1 to deprecated versions * rewrite img src to use azure blob storage in archive script Co-authored-by: rachmari <rachmari@users.noreply.github.com> * remove static files for ghes 3.1 * remove liquid conditionals and content for ghes 3.1 * remove outdated hardware reqs reusable * Fix liquid conditional uncaught by script * Close liquid conditionals missed by script * Apply @mattpollard's suggestions Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com> Co-authored-by: rachmari <rachmari@users.noreply.github.com> Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com>
1.3 KiB
1.3 KiB
title, shortTitle, intro, versions, topics, miniTocMaxHeadingLevel, allowTitleToDifferFromFilename
| title | shortTitle | intro | versions | topics | miniTocMaxHeadingLevel | allowTitleToDifferFromFilename | |||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Organization interactions | Organization | The Organization interactions API allows organization owners to temporarily restrict which type of user can comment, open issues, or create pull requests in the organization's public repositories. |
|
|
3 | true |
About the Organization interactions API
The Organization interactions API allows organization owners to temporarily restrict which type of user can comment, open issues, or create pull requests in the organization's public repositories. {% data reusables.interactions.interactions-detail %} Here's more about the types of {% data variables.product.product_name %} users:
- {% data reusables.interactions.existing-user-limit-definition %} in the organization.
- {% data reusables.interactions.contributor-user-limit-definition %} in the organization.
- {% data reusables.interactions.collaborator-user-limit-definition %} in the organization.
Setting the interaction limit at the organization level will overwrite any interaction limits that are set for individual repositories owned by the organization. To set different interaction limits for individual repositories owned by the organization, use the Repository interactions endpoints instead.