11–20 of 20 posts
I really like this, PR's are a crucial part of my workflow and they are one of the few notifications that I actually don't mind getting.
For comments, I go to https://github.com/notifications
Maybe if I had hundreds of pull requests per week I would need something more elaborate, but for my current situation it's enough.
I never check my email for these.
> This application requires OS X 10.9 or later. :(
This is awesome, well done! I just wanted to chime in and say I like your approach of just focusing on pull requests. There's another app I know of that just focuses on creating issues ( http://issuepostapp.com ). I happen to be the author of another GitHub Issues client ( http://neat.io/bee/github-issues-client.html ) which is aimed at the other end of the spectrum: to be full-featured. Great to see all these differ…
Definitely will give it a try, to get and idea whether I should part with those $49. Could well be the case to intense Githubbers.
For pull requests, I go to https://github.com/dashboard/pulls/ For comments, I go to https://github.com/notifications Maybe if I had hundreds of pull requests per week I would need something more elaborate, but for my current situation it's enough. I never check my email for these.
Different workflows and environements, different tools.
As far as I'm concerned, I find Trailer handy even for my weekend side projects as it lets me reply to PRs and comments from contributors more quickly (I might forget refreshing Github's web UI, and emails, well...).
YMMV may vary of course. We're just glad to offer you an extra option :)
For pull requests, I go to https://github.com/dashboard/pulls/ For comments, I go to https://github.com/notifications Maybe if I had hundreds of pull requests per week I would need something more elaborate, but for my current situation it's enough. I never check my email for these.
I've never been a big fan of email for things like this because they can get pretty noisy. To solve the having to track a lot of pull requests problem with minimal noise, I decided to go with a more self serve approach. The idea is to let users create logical groups for tracking pull requests. Below is an example of a logical group that lets you track individual pull requests from 6 different repos.
http://ny.testdrive.gitsense.com/index?#pid=24&cid=29&trail=
If you click on the links in the black bar, you can see how you can control the amount of noise. Everything is programmable so you can have it display whatever you want.
- Make the Pref / About etc. submenu an expandable item from the main menu instead of requiring an extra click (I know you were going for minimalism but it's not that intuitive)
- In the pref window list all the sorting options instead of adding a toggle for reversing direction
- Prompt to create or enter a token immediately on first run
- Auto load project list if there is no cache of it
I like it! Some suggestions: - Make the Pref / About etc. submenu an expandable item from the main menu instead of requiring an extra click (I know you were going for minimalism but it's not that intuitive) - In the pref window list all the sorting options instead of adding a toggle for reversing direction - Prompt to create or enter a token immediately on first run - Auto load project list if there is no cache of it