In brief
- General availability was announced on October 23.
- Permissions should match a specific task.
What GitHub announced
On October 23, GitHub announced general availability for enterprise installations of GitHub Apps. It expanded the administrative functions that apps can automate, including repository policies, rulesets, and authentication requirements. For GitHub Enterprise Server, the company says these changes will arrive in version 3.24.
This announcement is aimed at people managing enterprise accounts. It does not describe a Mexico-specific launch or a new feature that everyone with a personal account needs to enable.
Match access to the task
A GitHub App is an integration that can perform authorized actions. The documentation recommends granting only the permissions it needs. Access is divided into repository, organization, enterprise, and account permissions; those levels are not interchangeable.
Imagine a tool that organizes incoming work requests. Before installing it, write down what it needs to read and what it may change. That short list helps you discuss the integration with your administrator without understanding every detail of an API.
Check before installing
GitHub recommends checking who built an app and reviewing its requested permissions. Installing an app and authorizing it to act on your behalf are separate decisions. When an app changes its permissions, the account owner must approve the new ones; until then, the installation keeps its existing permissions.
For a small team, a useful review can start with three questions: who needs it, for which task, and who will check the result? Keep the answers with your internal documentation. If nobody can explain a particular permission, pause the installation and ask before a convenient tool becomes something the team depends on.
Sources and context
Sources used for this article. Follow the links to read the original material.
See the linked sources for more information. Corrections and contact →
