listing of stands without service stands

Question

listing of stands without service stands

MichalPP opened this issue 7 years ago · 8 comments

command.php?action=map:markers should return only stands which are available for general use (so service stands should be removed, or marked as unavailable in some way other than name).

Answer 1 · 2017-11-19T16:18:44.000Z

This is regarding breakthrough release that has not been developed for some time. Laravel version has priority instead, any testing should be done on the develop branch.

Answer 2 · 2017-11-19T16:24:04.000Z

where should I put this issue? afaik it is impossible to add issues to branches

Answer 3 · 2017-11-19T16:37:12.000Z

Branch is not developed anymore, but you are welcome to do the pull request with the change.

…

On Sun, Nov 19, 2017 at 5:24 PM, MichalPP ***@***.***> wrote: where should I put this issue? afaik it is impossible to add issues to branches — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#129 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIJ3zcrRaSPyGr_c-GbMPHXvZjd4vzzhks5s4FYlgaJpZM4Qjb4c> .

Answer 4 · 2017-11-19T19:04:24.000Z

which branch is developed? where should I put this issue?

Answer 5 · 2017-11-20T07:41:32.000Z

develop, and add label laravel

Answer 6 · 2017-11-20T08:28:04.000Z

as I've noted above, it is impossible to add issues to branches and I (as non root) cannot add labels.

Answer 7 · 2017-11-20T08:37:11.000Z

ok, I created new issue for laravel version #130

Answer 8 · 2018-01-22T11:09:47.000Z

None of this makes sense to me. In GitHub, bugs apply to the whole repository, there isn't any way to specifically create a bug which would apply to a branch only, and @MichalPP hasn't done anything wrong. There wasn't need to open a new issue.