GitHub Pro Tips for Projects with Multiple Repositories

GitHub Pro Tips for Projects with Multiple Repositories
A good practice when working with multiple services in the same project is to create a new repository for each service. And since GitHub changed the pricing from “per repo” to “per user”, companies were not restricted to 10 repositories any longer to save money.

When we started with 5–6–7…10 node.js services for a single organization, we faced the issue on how to manage issues and pull requests. Not always is there a notification of new issues or PRs. There are external services like ZenHub and Waffle.io to handle this, but it’s much easier on GitHub directly, by “hacking” GitHub Issues. Here are some examples for the “Node.js” organisation (replace nodejs with your organisation name):

Show all open issues for the whole organisation/project

  • is: open
  • is: issue
  • user: nodejs
  • archived: false
  • sort: updated-desc
https://github.com/issues?q=is%3Aopen+is%3Aissue+archived%3Afalse+user%3Anodejs+sort%3Aupdated-desc

Show all open Pull Requests for the whole organisation/project

  • is: open
  • is: pr
  • archived: false
  • user: nodejs
  • sort: updated-desc
https://github.com/pulls?q=is%3Aopen+is%3Apr+archived%3Afalse+user%3Anodejs+sort%3Aupdated-desc+

Open these links together with your most important, project related websites (and GitHub Notifications), and (in Safari) click “Bookmarks -> Add Bookmarks for These Tabs” and save in your Favorites. When you click on the bookmark, all tabs will open the same time and you get a great overview of your project, open issues, PRs and what’s going on!