Gitscout - A beautiful Github Issues experience for macOS

@sofistixy My developer friend use SourceTree too! I would pass this to him to see how he think!

thanks @pauliebeck! would love to hear his feedback! 😀

hi @sofistixy, thank you for asking. 🙂 I might be wrong but I think SourceTree is a more a Git client (similar to Github Desktop) rather than an "Issues Manager". You basically can't visualize, browse and manage your issues in SourceTree, as much as you can't create branches, and manage your Git repository with Gitscout. So I think it's safe to say that we're not actually competing against SourceTree 😉

Hi @adamslieb, thanks! Integrating with ZenHub could definitely be something to consider, but I think we would work on supporting Github "official" features first (read "Github Projects" 😉) to provide a deeper integration rather than with a 3rd party app.

@jeremybenaim Maybe. In my small circle of the universe Zenhub has a large following of companies who use it exclusively. If more of those are/would be users of yours, especially potentially paying users, maybe it should be prioritized higher. I have no clue what your user base looks like, just a thought. Also selfishly, I'd love a Zenhub desktop product :)

@mehulkar Yes we definitely need to investigate how to make Gitscout available for Enterprise user! And we will sure let you know when it's available 😉

@benguild hello Ben. We don't support offline and sync yet but this is on our roadmap. 🙂

@jeremybenaim It's a significant architectural change. Maybe you can let people save actions as "drafts" sort of like the outbox on Outlook.

@benguild the app is kinda ready for that, we just didn't work the whole synchronisation thing (which is the trickiest part). But yea, we will definitely provide offline support for Gitscout 😉

hey @chakkaradeep, thanks! 😊 Funny that you're mentioning a menu bar icon with a mini window, because the first version of Gitscout (from last year!) was exactly that. But we figured that the experience wasn't comprehensive enough so we ended up building a "full window" app instead.