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, allowTitleToDifferFromFilename, intro, versions, topics, miniTocMaxHeadingLevel
| title | shortTitle | allowTitleToDifferFromFilename | intro | versions | topics | miniTocMaxHeadingLevel | |||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| User interactions | User | true | The User interactions API allows you to temporarily restrict which type of user can comment, open issues, or create pull requests on your public repositories. |
|
|
3 |
About the User interactions API
The User interactions API allows you to temporarily restrict which type of user can comment, open issues, or create pull requests on your 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 %} from interacting with your repositories.
- {% data reusables.interactions.contributor-user-limit-definition %} from interacting with your repositories.
- {% data reusables.interactions.collaborator-user-limit-definition %} from interacting with your repositories.
Setting the interaction limit at the user level will overwrite any interaction limits that are set for individual repositories owned by the user. To set different interaction limits for individual repositories owned by the user, use the Repository interactions endpoints instead.