Skip to content
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

[META] Ideas 💡 #2

Open
12 of 84 tasks
moul opened this issue Feb 6, 2020 · 3 comments
Open
12 of 84 tasks

[META] Ideas 💡 #2

moul opened this issue Feb 6, 2020 · 3 comments
Assignees
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Projects

Comments

@moul
Copy link
Member

moul commented Feb 6, 2020

Front Improvements

Back Improvements

Code Quality

Doc

Testing

@moul moul self-assigned this Feb 6, 2020
@n0izn0iz
Copy link

n0izn0iz commented Feb 6, 2020

It would be nice to see the branch that triggered the build on the cards on the front page

@moul moul added the help wanted Extra attention is needed label Mar 2, 2020
@ekelen
Copy link
Collaborator

ekelen commented Apr 16, 2020

Can we add limit and sort params to http requests? (If not already there?)

@ekelen
Copy link
Collaborator

ekelen commented Oct 2, 2020

Add a mergerequest_list route (or sort/group query param)?

It could be for the API; since the whole feed is sorted by MR now in UI, a backend supporting this would eliminate some fragile data transforms in the front.

I guess an alternative is that this could just go in the URL bar on the front; at least it will clarify the organization for users (it's currently weird to ask limit=10 and get two visual blocks/cards, but with group_by=mergerequest it becomes clear).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Projects
META
Ideas 💡
Development

No branches or pull requests

3 participants