4 ms·
Good point regarding automatically marking as read. Since there is already a “Mark as Read” button, automatically doing so would not required for my ideal solu
by alanh 16y ago
Good point regarding automatically marking as read.
Since there is already a “Mark as Read” button, automatically doing so would not required for my ideal solution (as described in the link).
I have heard people describe notifications as “broken” for not auto-marking as read, which is why I assumed it was desirable. (That, and since Facebook does it this way, there is a very popular precedent and likely some broken expectations among new GitHub users.)
Now regarding labels/folders… this is probably overkill IMO. That’s where GitHub "issues" or various To-do managers, which do have labels, come in.
- Groxx 16y agoI'm not familiar with the "issues"... I'm a very light GitHub user. So, a couple questions for you: Issues? Does GitHub have an API for their notification / message / what-have-you system(s)? What do you use the to-do managers to do? How do they help? Are there any other ways the notifications are "broken"? I ask because I may be interested in making a Safari plugin (which I gather is pretty trivially similar to making a Chrome plugin) to handle a few of the basics. And I'm a UI/UX nut, so how others handle workflow things like this fascinate me.
- steveklabnik 16y agoIssues is GitHub's built in ticket system. Se here, for example: http://github.com/hacketyhack/hacketyhack/issues http://github.com/hacketyhack/hacketyhack/issues They can be turned on per-project.