This guide is focused on getting the best out of GitHub as a tool.
In Engineering, you will find related content on how we use GitHub to implement our desired work methodology and product engineering culture.
Notification
Recommendations for best-managed GitHub notifications:
-
Disable Pull request push notifications https://github.com/settings/notifications
Pushes create a lot of noise, they usually leave PRs in an incomplete state.
Instead, you can wait for the author of the PR to ask for a new review.
If you would rather regularly check the progress of a task, you can snooze the previous notification for x days rather than wait for pushes.
-
Use email notifications; don't use GitHub notifications UI. This is because:
- Gmail UI is much faster
- Gmail has filter rules to remove spam notifications
- Gmail allows you to snooze notifications, which is very helpful when delegating tasks to community members
Gmail filters
If you are using email to manage notifications, we recommend enabling a few filter rules to reduce noise:
Public organization
While you can see the following:
-
On your profile page:
-
GitHub issues and PRs:
The community can’t see that you are part of the MUI organization. By default, GitHub makes any new member of an organization private on their profile, so the community will see this instead:
This can be problematic because it means that the community doesn’t know exactly who they are talking to, e.g., who they are receiving an answer on their GitHub issue from or who left a review on their PRs. They might confuse you with a user of the library.
More transparency can help; you can make this visible by**:**
