How to correctly receive GitHub emails

How to correctly receive GitHub emails
Background

The development process of our factory is usually based on GitHub. Review code on GitHub is also an important part of my daily work. For me, the most annoying part in the code review process is that I comment on or @ people under the pull request or commit, and there is always no echo. I asked the client afterwards that their reply was often "I Don't Know You @ me ~".

This makes me very angry. Therefore, I decided to write a document to everyone to avoid missing important GitHub messages. People who will not reply to me on GitHub will be able to close the discussion!

 

GitHub notification mechanism

 

Notification Type and Method

In either case, we will receive a notification from GitHub.

• Watching: After paying attention to a project, it is equivalent to subscribing to all updates of the project, I will be notified of the new release, new issue, new PR and all discussions of this project.

• My participation: When I participate in an issue, PR, or commit discussion, or be @ by someone else, I will continue to receive subsequent updates to this discussion.

The latter case seems to be more important to me. If you do not need to closely follow a project, I should avoid following it.

In addition, GitHub will notify us in the following two ways:

• Insite email (Web): When I log on to the GitHub website, if there is a new message, a small blue dot will be displayed in the navigation bar. Click in to see the detailed notification.

  Insite email inbox

• Email: The notification will be sent directly to my mailbox, and the direct reply effect is equivalent to logging on to the relevant page to reply, which is very convenient.

It can be seen that the former is passive and the reminder capability is too weak. The latter is proactive push with good timeliness, but what I need to note is to control the message density to avoid bombing. Therefore, let's take a look at GitHub's "auto-attention" function.

 

Automatic follow

Important messages are good. First, it means that messages that are irrelevant cannot be lost. If you often receive a lot of GitHub messages, you may not read them all. Therefore, we need to turn off the "auto-attention" function.

Log on to the GitHub notification center page to disable this function:

Automatic follow-up

Why shut down it? This function is very interesting. Every time you get the push permission for a repo, GitHub will automatically help you follow this repo. This is useful in the open-source community, because when you obtain this permission, it often means that you become the core Maintainer of this repo, and you really need to grasp every step of this project.

However, this is not suitable for internal projects of the company. For example, our main site project is a private repo, and almost every engineer in the company fork it. At the same time, for collaboration, each fork needs to open read and write permissions to all engineers. Therefore, you will automatically pay attention to the nearly repo, and any breeze from these repo will inform you, even if you are not actually working on the fork of other colleagues.

In short, to prevent irrelevant messages from bombing you, turn off the automatic attention function. You may have followed a bunch of irrelevant forks. Please remember to cancel them one by one on your follow list page. (If you are not the core administrator, we recommend that you remove the upstream of the main site project .)

 

Personal settings

After learning about GitHub's features, we can make specific configuration and selection.

 

Set Email

Under normal circumstances, each person will open his/her work mailbox during work hours. First, make sure that the GitHub message is sent to this email address. Since each GitHub account is often not registered using a work email address, we need to correct the email address.

Log on to the GitHub mailbox settings page and add your work mailbox. Then, you will receive a verification email from your work mailbox. After verification, your GitHub account is bound to two mailboxes.

Account mailbox settings

(You do not need to set this work mailbox as "primary", as long as the verification is passed .)

At this point, we will prepare for Email.

 

Notification center

Next, go to the GitHub notification center and select a notification method for two different types of notifications. Make sure that at least the first "Email" is selected:

Notification Method settings

Next, select the email address that receives the email notification. Select the work mailbox we just added and save it.

Notification Email settings

(The mailbox settings here only affect message receipt and account identity .)

All right, all done. From then on, all important GitHub messages will be sent to your work mailbox. Finally, I will tell you a few tips. I believe you can use them.

 

Reduce interference

 

Remove a Repo

You have already mentioned your follow list, where you can clean up projects that are no longer important at any time. At the same time, go to the page of any project, you can choose to pay attention to it in the upper right corner.

Repo follow options

"Not watching" means that you will Not receive notifications that are irrelevant to you. You will still receive a notification if there is a new reply to your discussion (you initiated, actively participated or.

Do not select "Ignoring", which means that you cannot receive important messages.

 

Cancel a discussion

When there is no more to you in a discussion, but there are still more and more messages coming in, block it. Click the "Unsubscribe" button shown in the following figure from the link to the webpage of the message mail to cancel the discussion.

Unsubscribe-1

Unsubscribe-2

 

Lock a discussion

When an issue or PR is no longer necessary for further discussion, you can lock it-only if you have to be the repo administrator.

 

Shield someone

If you encounter bored people always harass you, you can go to its user page to block and report it.

 

Conclusion

I believe that you have a good understanding of the GitHub notification mechanism, and you should be able to flexibly configure the methods for receiving GitHub messages.

Okay, that's it. If you still don't reply to me later, you will be rejected.

For more GitLab tutorials, see the following:

GitLab Installation Guide in Ubuntu 14.04

How to install Gitlab in Ubuntu Server 14.04

Install GitLab in Chinese with CentOS source code

Install GitLab on Ubuntu 12.04

GitLab 5.3 upgrade considerations

Deploy GitLab on CentOS (self-managed Git project repository)

Install GitLab 6.0.2 on RHEL6/CentOS6/ScientificLinux6

CentOS 6.5 GitLab installation tutorial and Related Problems

GitLab details: click here
GitLab: click here

This article permanently updates the link address: