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.2 KiB
1.2 KiB
title, shortTitle, intro, versions, topics, miniTocMaxHeadingLevel, allowTitleToDifferFromFilename
| title | shortTitle | intro | versions | topics | miniTocMaxHeadingLevel | allowTitleToDifferFromFilename | |||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Repository interactions | Repository | The Repository interactions API allows people with owner or admin access to temporarily restrict which type of user can comment, open issues, or create pull requests in a public repository. |
|
|
3 | true |
About the Repository interactions API
The Repository interactions API allows people with owner or admin access to temporarily restrict which type of user can comment, open issues, or create pull requests in a public repository. {% 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 repository.
- {% data reusables.interactions.contributor-user-limit-definition %} in the repository.
- {% data reusables.interactions.collaborator-user-limit-definition %} in the repository.
If an interaction limit is enabled for the user or organization that owns the repository, the limit cannot be changed for the individual repository. Instead, use the User or Organization interactions endpoints to change the interaction limit.