article

GitHub Pro Tips for Projects with Multiple Repositories

16 Apr 2018 | 1 min read

big archive full of colored office binders

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!

If you have any questions or comments, please reach out on Twitter or start a discussion on GitHub.

Patrick Heneise

Chief Problem Solver and Founder at Zentered

I'm a Software Enginer focusing on web applications and cloud native solutions. In 1990 I started playing on x386 PCs and crafted my first “website” around 1996. Since then I've worked with dozens of programming languages, frameworks, databases and things long forgotten. I have over 20 years professional experience in software solutions and have helped many people accomplish their projects.

pattern/design file