6.4 GitHub-Managing organizations

Management Organization

In addition to personal accounts, GitHub also provides an account called an organization (organizations). Organizational and personal accounts have a namespace for storing items, but many other things are different. An organizational account represents a group of people who have multiple projects together and also provides tools for grouping members. Typically, such accounts are used for open source groups (for example, "Perl" or "rails"), or companies (for example: "Google" or "Twitter"). basic knowledge of the organization

We can simply create an organization by clicking on the "+" icon in the upper right corner of any GitHub page and selecting "New Organization" in the menu. Figure 6-45. "New Organization" menu item

First you must provide the organization's name and the organization's primary contact mailbox. Then, if you want, you can also invite other users as co-owners.

Once you've completed the above steps, you'll have a whole new organization. Similar to a personal account, you can use this Organization for free if all of the organization's content is open source.

As an organization's owner, when you derive a repository, you can choose to derive it into the namespace of your organization. When you create a new repository, you can store it in your personal account or in an organization you own. At the same time, you will automatically "focus" on all new repositories within these organizations.

Like Avatar, you can upload avatars for your organization and make it more personal. Also, like a personal account, the organization has a landing page (landing page) that lists all of the Organization's repository, and that page is available for everyone to browse.

Below we say some organizations and individual accounts are different places. Team

The organization uses the team (TEAMS) to manage members, which is a set of personal accounts and repositories in the organization, as well as team members ' access to those repositories.

For example, suppose your company has three repositories: frontend, backend, and deployscripts. You will want your html/css/javascript developer to have access to frontend or backend, and the operator to have backend and deployscripts access rights. The team makes this task easier without having to manage its collaborators for each repository.

The Organization page consists primarily of a panel (dashboard), which contains all the repositories, users, and teams within the organization. Figure 6-46. Organization page

You can manage your team by clicking on the Team Sidebar (Teams) on the right side of figure 6-46. After clicking, you will enter a new page where you can add new members and repositories to your team, or manage your team's access and other settings. Each team can have read-only, read-write, and manage three permissions for the repository. You can change the appropriate permission level by clicking the "Settings" button in Figure 6-47. Figure 6-47. Team Page

When you invite a user to join the team, the user receives an email notifying him of the invitation.

In addition, the team is similar to a personal account, with the ability to @mentions (for example: @acmecorp/frontend), except that all members of the mentioned team will be subscribers to the topic. This feature is helpful when you want to get the attention of someone in your team and don't know exactly who to ask.

A user can join any number of teams, so don't confine yourself to a team that has access control. Teams with special concerns, like ux,css or refactoring, are helpful for a class of subjects, and legal and colorblind are all about their respective fields. Audit Log

The owner of an organization can also access all information about what is happening in the organization. On the Audit Log tab There is a log of the entire organization and you can see who is doing what in the world. Figure 6-48. Audit log

You can also filter logs by selecting a certain type of event, somewhere, or someone.