Githawk: What unique features should we focus on?

Created on 20 Nov 2017  ·  8Comments  ·  Source: GitHawkApp/GitHawk

Now that we are getting close to having most of GitHub’s core productivity features, what can we build to set us apart? Maybe even make using GitHawk more enjoyable than the web?

Some ideas:

  • Partnership with Working Copy for 2-way deep linking
  • Offline syncing
  • Canned replies
  • Editing code and creating PRs
  • CI integration
  • Push notifications

_What else?_

This is just to get ideas flowing. We won’t start any of this until sometime next year.

Sent with GitHawk

❔ question

Most helpful comment

It already is @mattcantstop 😉

Sent with GitHawk

All 8 comments

  1. Editing code and creating PRs
  2. CI Integration

Push Notifications

Working Copy partnership is a really interesting idea!

  • PR status/merging/CI integration
  • Customisable Push Notifications (Turn them on/off on a 1:1 basis, not tied to subscription, I want some to appear in-app but not push notify me!)
  • Better filtering and searching (Mobile web really lacks this)
  • Stale Issues/PRs and more unique management features like duplicate detection and chase approvals

What would also be nice is to detect if an issue belongs to a PR and vice versa.

What I would love is that if I'm read up on an issue related to a PR and I am read up on said PR, to automatically mark both as read. On web eg., the issue will still be unread because of the close event triggering a notification.

Notifications 😝

Re issue+PR connection detection: it seems like this is pretty feasible looking at the GraphQL response:

{
              "__typename" : "CrossReferencedEvent",
              "id" : "MDIwOkNyb3NzUmVmZXJlbmNlZEV2ZW50NTM4MTk5NzQx",
              "actor" : {
                "login" : "BasThomas",
                "__typename" : "User"
              },
              "source" : {
                "__typename" : "PullRequest",
                "title" : "[DO NOT MERGE] Switch markAll logic back to mark all",
                "number" : 1295,
                "closed" : false,
                "merged" : false,
                "repository" : {
                  "name" : "GitHawk",
                  "owner" : {
                    "login" : "rnystrom",
                    "__typename" : "User"
                  },
                  "__typename" : "Repository"
                }
              },
              "createdAt" : "2017-12-20T07:35:26Z"
            }

One of my favorite features of GitHawk is that I need to explicitly mark a notification as read. If you ever change that behavior, please let it be something that can be configured in the settings.

Thanks again for making this app! ♥️

It already is @mattcantstop 😉

Sent with GitHawk

Was this page helpful?
0 / 5 - 0 ratings

Related issues

BasThomas picture BasThomas  ·  3Comments

rnystrom picture rnystrom  ·  3Comments

BasThomas picture BasThomas  ·  3Comments

rnystrom picture rnystrom  ·  3Comments

BasThomas picture BasThomas  ·  3Comments