-
Notifications
You must be signed in to change notification settings - Fork 196
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add buttons for different query #44
Comments
This is a good idea. But where could we source the info from? Would it be a
form you fill out? That is, how does the code know what labels or repos are
available?
…On Tue, Oct 2, 2018 at 12:17 AM Avkaran Singh ***@***.***> wrote:
In https://code.publiclab.org/ here we can see issue only by add query in
that link bar ,Add button's for that every possible query where user can
search issue in every single repository, all repos, by just click the button
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#44>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/AABfJxA4YRhLwNbx5Xkrb4O9X9UlUYOxks5ugui-gaJpZM4XDTYx>
.
|
It can be a dropdown...filling some input for repo name to search issues from seems like an extra work with less visual indication...because in case of an input, we have to deal with random words typed in the input and dropdown will save people from typing names and remembering spellings, lol 😜 |
@Rishabh570 if you give a brief info on implementing this, I can work on it 😄 |
Showing issues as per provided labels would require us to store the list of issues for that particular repository in the database which means deviating from the Till then, @pydevsg you can take a look at other issues available across our organization. Some Thanks! |
In https://code.publiclab.org/ here we can see issue only by add query in that link bar ,Add button's for that every possible query where user can search issue in every single repository, all repos, by just click the button
The text was updated successfully, but these errors were encountered: