listing of stands without service stands

[MichalPP]

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).

[nekromoff]

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.

[MichalPP]

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

[nekromoff]

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> .

[MichalPP]

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

[jozefbalun]

develop, and add label laravel

[MichalPP]

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

[jozefbalun]

ok, I created new issue for laravel version #130

[andrewshadura]

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.