Shelley Vohr

This shouldn't be mediated by the version of macOS - you need to be building against the 10.15 SDK. You can _run_ this on any version of macOS as long...

Unfortunately the GitHub REST API is pretty rough around the edges for Notifications - [the result payload](https://docs.github.com/en/free-pro-team@latest/rest/reference/activity#list-repository-notifications-for-the-authenticated-user) doesn't contain that information at present. I'm fairly certain the GraphQL version does,...

@ianaya89 ooh, thanks! Sometimes GitHub does this - they add new types without documenting them. I'm not sure we can properly fix up the links, since GitHub doesn't fill in...

@broccolism my personal recommendation would be to create and use a [Personal Access Token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token). You can then authorize a given token for specific organizations as needed. For example, I have...

hmm - i'm on the same version and i've not had to manually refresh 🤔 do you have a gif or something demonstrating the behavior?

I'd be fine with this unless @manosim would prefer to leave it as is :)

This is the current login screen - it specifies the scope needed: `notifications`. What other information would you expect here if you feel this is insufficient?

For some context - the issue here lies with the GitHub V3 API, which fails to return a url for the notification endpoint when the notification type is a ci...

@martinjagodic the issue lies unfortunately with GitHub - the Notifications API is somewhat......lacking in many areas. The payload for a call to [fetch notifications for an authed user](https://docs.github.com/en/rest/reference/activity#list-notifications-for-the-authenticated-user) has a...

hey @Araxeus - this is great work but it's a bit much for one PR. Can we split this up so we can more effectively review? For example, es2020 upgrade...