Difference between revisions of "GitHub organization"

From wikieduonline
Jump to navigation Jump to search
Line 14: Line 14:
 
** Write: Recommended for contributors who actively push to your project
 
** Write: Recommended for contributors who actively push to your project
 
** Maintain: Recommended for project managers who need to manage the repository without access to sensitive or destructive actions
 
** Maintain: Recommended for project managers who need to manage the repository without access to sensitive or destructive actions
** Admin
+
** Admin: Recommended for people who need full access to the project, including sensitive and destructive actions like managing security or deleting a repository
  
 
== Related terms ==
 
== Related terms ==

Revision as of 10:23, 23 March 2022

Organization Roles

  • Owners
  • Members
  • Billing managers
  • Security managers (beta as Jan 2022). It gives every member of the team permissions to manage security alerts and settings across your organization, as well as read permissions for all repositories in the organization.
  • Outside collaborators


  • Repository roles: https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization
    • Read: Recommended for non-code contributors who want to view or discuss your project
    • Triage: Recommended for contributors who need to proactively manage issues and pull requests without write access
    • Write: Recommended for contributors who actively push to your project
    • Maintain: Recommended for project managers who need to manage the repository without access to sensitive or destructive actions
    • Admin: Recommended for people who need full access to the project, including sensitive and destructive actions like managing security or deleting a repository

Related terms

See also

Advertising: