Agree. And seems like GitHub API does provide this.

[upvote button pressed]

Nice one that you close my issue and point me to an issue that is 4 month old with no movement?

But what is the point to have two separate issues/discussions leading to the same result? :) This one does not have movement cause it's currently labeled as v2.0. If you think that this issue is a stopper for a v1.0 release, let us know.

@gwsdesk - Trying to keep duplicates to a minimum too.

Currently, one can go to the GitHub item and subscribe to notifications (the button now has a prominent place in the sidebar of issues). A similar button in the website would surely be ideal, and it was something I had started looking at over the weekend but I found the Notifications API somewhat confusing. Need to look at it again.

How can i know than that a reply is made to test a patch available on
Github? Seems like important to me?
On 3/4/2014 3:27 PM, Dmitry Rekun wrote:

But what is the point to have two separate issues/discussions leading
to the same result? :) This one does not have movement cause it's
currently labeled as v2.0. If you think that this issue is a stopper
for a v1.0 release, let us know.

—
Reply to this email directly or view it on GitHub
#168 (comment).

Thanks Michael I understand the reasoning but as posted in my reply to
B2B the only way to do this indeed is subscribe to notifications on
Github I am aware of that but for me as explained before I think it is
essential since I assume (?) that as on Joomlacode we would request
testing through an update on Issue of the new Tracker item. They Issue
and Github) won't be synchronized with replies me think so if you post
an update on Issue with a request to test how can people know (if they
don't have a Github account? and me think many don't have one?)

(side note: Do you ever sleep? :) )
On 3/4/2014 3:36 PM, Michael Babker wrote:

@gwsdesk https://github.com/gwsdesk - Trying to keep duplicates to a
minimum too.

Currently, one can go to the GitHub item and subscribe to
notifications (the button now has a prominent place in the sidebar of
issues). A similar button in the website would surely be ideal, and it
was something I had started looking at over the weekend but I found
the Notifications API somewhat confusing. Need to look at it again.

—
Reply to this email directly or view it on GitHub
#168 (comment).

There isn't a separate login mechanism for the issue tracker; it uses GitHub authentication only. So, everyone will be required to get GitHub accounts if they don't already (which isn't a bad thing, there's a lot of projects here; ever wanted to report a Bootstrap bug?). This allows us to use their notification system for updates on tracker items. I'm posting this comment via the live website, note where the e-mail notification comes from ;-)

So, the only thing missing right now is having that similar Subscribe button that's available on GitHub built into the website. Not that bad right now compared to other things (like actually ensuring our ACL setup suits what is needed, ensuring the UI is correct, the current feature set is working right, etc.).

I do sleep on occasion. My humanity is commonly called into question around this project, apparently some believe I'm actually a bot. But, 3 AM does sound like an acceptable bedtime for today ;-)
You may blame the J!Tracker Application for transmitting this comment.

I had started looking at over the weekend but I found the Notifications API somewhat confusing.

Same for me. About two weeks ago I also wanted to dig in, but nothing :) Decided that we have more prior features to implement.