Use fixed and fluid containers depends on page content
Designs
- Show closed items
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- username-removed-444 mentioned in merge request !1161 (merged)
mentioned in merge request !1161 (merged)
- Author Owner
- Owner
- Maintainer
@dzaporozhets In the first screenshot the
Gitlab.org/Gitlab Community Edition
at the top should also be aligned with the remaining page. Having only that at the left looks weird. :) - Contributor
i love love love this @dzaporozhets
- Author Owner
- Owner
- Maintainer
@rspeicher That's exactly what i meant
- Owner
@haynes Sorry, I don't always read the whole thread :)
- username-removed-444 Reassigned to @dzaporozhets
Reassigned to @dzaporozhets
- username-removed-444 mentioned in merge request !1207 (merged)
mentioned in merge request !1207 (merged)
- Author Owner
So far I think about side-by-side diff as the only candidate for full-width layout. If someone has other pages to suggest - you are welcome.
- username-removed-444 Milestone changed to 8.0
Milestone changed to 8.0
- username-removed-444 Status changed to closed by commit ef1776b8
Status changed to closed by commit ef1776b8
- username-removed-444 mentioned in commit ef1776b8
mentioned in commit ef1776b8
Hi @dzaporozhets,
the build details page would be great to. Right now, display is very unreadable for composer dependencies downlaod and for your behat test.
Here is a screenshot with container-limited class and without
- Author Owner
@nicolas-bastien I agree it makes sense to use fluid layout for build trace. Feel free to contribute it