Many of us use Github daily however we usually don't use all its features. On the latest months, its team released a few webinars about how Github uses Github. More than showing the web interface, they talked about their culture and their workflows. In this post, I'm adding the links to the webinars with a few notes.
- They don’t send email internally and they use repositories for everything
- They have 688 people and 829 teams - the concept of team here is: by organizational team, by project, by affinity and by location
- Their projects always have:
- In PRs they include a TL,DR (I also do this)
- It is possible to create accordions / dropdown in Markdown - example
- “Remote” is not a good word and they prefer using the term “Distributed” - which I also like. Like Thinkific, they have weekly radars and team stand-ups. It is interesting to mention they use their own Github to handle projects, instead of using a project-specific tool like Jira or Asana. Even their one-on-ones are stored in repositories
- They mentioned Hubot - a bot system with several plugins
- For video calls, they use zoom - for all meetings they book they also add a zoom link (we kind of do the same with Google Meet)
- They show the project's functionality inside Github. It is a Kanban/Trello style project tool with the advantage of being integrated with Github. To be honest, I never noticed the Project feature but after this webinar, I started using in a pet-project
- They show Probot - it’s an open-source bot created by GH employees
- They show Task Lists (markdown trick)
- This one covers pretty much the project feature that Github offers (similar to the previous one). It is cool because projects are connected to the repo and they show how to use Issues, PRs and Milestones together. For one moment I thought why we don’t use Github in the company but I remembered how much would cost per user so I am not sure if it is a good idea.
- Github has saved replies that can be used in PR’s and Issues. Pretty handy.
- They show Read the Docs
- They remember that documentation is part of a process, don't give this to only one person.
- They share some thoughts about how to write good documentation.
If you like my notes you may want to watch the videos