创建组织时会自动创建 "developers" 团队。默认情况下,开发团队对组织范围内创建的所有新包具有读/写访问权限。
¥The "developers" team is automatically created when you create an organization. By default, the developers team has read/write access to all new packages created under the organization's scope.
-
添加到组织的成员(包括组织所有者)将自动添加到开发者团队
¥Members added to the organization, including the organization owner, are automatically added to the developers team
-
组织范围内任何新创建的包的
package.json
中的maintainers
字段 都会自动填充当前开发团队的成员¥The
maintainers
field in thepackage.json
of any newly created packages under the organization scope is automatically populated with the members of the current developers team
如果你在组织范围内创建新包,并且不希望开发者团队的成员拥有该包的读/写访问权限,则所有者或管理员可以删除开发者团队对该包的访问权限。欲了解更多信息,请参阅“管理团队对组织包的访问”。
¥If you create a new package under your organization's scope and you do not want members of the developers team to have read/write access to that package, an owner or admin can remove the developers team's access to that package. For more information, see "Managing team access to organization packages".
如果所有者向组织添加新成员并且不希望该成员加入开发者团队,则所有者可以将其删除。
¥If an owner adds a new member to an organization and does not want that member to be on the developers team, an owner can remove them.
注意:由于以下原因,开发者团队不能再从组织中删除:
¥Note: The developers team can no longer be removed from an organization for the following reasons:
-
它是组织中所有用户、包和默认权限的真实来源。
¥It is the source of truth for all users, packages, and default permissions in an organization.
-
当你想要限制写入权限时,最好将默认权限设置为只读并创建单独的团队来管理写入权限。
¥When you want to restrict write access, it is almost always better to set the default permissions to read-only and create separate teams for managing write permissions.