| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
| |
[ci skip]
|
| |
|
| |
[ci skip]
|
| |
|
| |
[ci skip]
|
| |
|
| |
[ci skip]
|
| |\ |
|
| | |
| |
| | |
[ci skip]
|
| |/
|
| |
It was already released, we do not have to wait until February!
|
| |
|
| |
[ci skip]
|
| |
|
| |
[ci skip]
|
| |
|
| |
[ci skip]
|
| |
|
| |
[ci skip]
|
| |\ |
|
| | |
| |
| | |
[ci skip]
|
| | |
| |
| | |
[ci skip]
|
| | |
| |
| | |
[ci skip]
|
| |/
|
|
| |
the author and mr fields got swapped,
see https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/8425#note_21021254
|
| |
|
| |
[ci skip]
|
| |
|
| |
[ci skip]
|
| |
|
| |
[ci skip]
|
| |
|
| |
[ci skip]
|
| | |
|
| |
|
| |
[ci skip]
|
| |
|
| |
[ci skip]
|
| |
|
| |
[ci skip]
|
| |
|
|
|
|
| |
[ci skip]
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| |
|
| |
[ci skip]
|
| |
|
| |
[ci skip]
|
| |
|
| |
[ci skip]
|
| |
|
| |
[ci skip]
|
| |
|
| |
[ci skip]
|
| |
|
| |
[ci skip]
|
| |
|
| |
[ci skip]
|
| |
|
| |
[ci skip]
|
| |\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Make milestone page responsive
Credit to @yury-n for this one. :star: :star2: :star: Original MR: !5255
## What does this MR do?
> Makes the milestone page more mobile friendly
## Are there points in the code the reviewer needs to double check?
> Shouldn't be but maybe double check that the views I changed are exclusively used by the milestone details page I was amending and not any other pages that I haven't tested after my changes.
Looks good to me. :) Would be awesome to have @annabeldunstone check up on the stylesheet updates.
## Why was this MR needed?
> Buttons were misaligned
> Progress bar was not 100% width
> Stats were cut in the middle
> Milestone name/date text overflow
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added
- [ ] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)
- [ ] API support added
- Tests
- [ ] Added for this feature/bug
- [ ] All builds are passing
- [ ] Conform by the [merge request performance guides](http://docs.gitlab.com/ce/development/merge_request_performance_guidelines.html)
- [ ] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides)
- [ ] Branch has no merge conflicts with `master` (if you do - rebase it please)
- [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)
## What are the relevant issue numbers?
Closes #18852
See merge request !6655
|
| | |
| |
| |
| | |
Corrected lines failed by linter
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
[ci skip]
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| | |
| |
| |
| |
| |
| | |
[ci skip]
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| | |
| |
| | |
[ci skip]
|
| | | |
|
| | |
| |
| |
| | |
This reverts commit 605d338acc19386ba7dfd5e57afd5542e40f70fb.
|
| | |
| |
| |
| | |
This reverts commit 5d4aeae9bf6650355e2db709bca0a96167f0ea25.
|
| | |
| |
| |
| | |
[ci skip]
|
| | |
| |
| | |
[ci skip]
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Remove project_title additions from builds and environments
## What does this MR do?
Removed soon-to-be un-needed project title additions from builds and environments.
**This MR depends on !5998, which introduces subnav to these pages. Without it we're just removing a useful link.**
## Are there points in the code the reviewer needs to double check?
@iamphill Is this right of me? One of these still exists in `projects/artifacts/browse`, I'm not sure whether to fix the issue with `project_title`, which already has some issues with its chevron, or just remove it as it will soon be redundant.
## Why was this MR needed?
## Screenshots (if relevant)
**BEFORE:**
**AFTER:**
## Does this MR meet the acceptance criteria?
- [x] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added
- [ ] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)
- [ ] API support added
- Tests
- [ ] Added for this feature/bug
- [ ] All builds are passing
- [x] Conform by the [merge request performance guides](http://docs.gitlab.com/ce/development/merge_request_performance_guidelines.html)
- [x] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides)
- [x] Branch has no merge conflicts with `master` (if you do - rebase it please)
- [x] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)
## What are the relevant issue numbers?
Closes #21764
See merge request !6160
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
environments
Removed unneeded `project_title` code and last reference
Added CHANGELOG entry
|
| | | | |
|
| | | |
| | |
| | | |
[ci skip]
|
| | | |
| | |
| | |
| | | |
[ci skip]
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Change auto selection behaviour of emoji and slash commands to be more UX/Type friendly
## What does this MR do?
In the context of a special command (starting with "/", ":", ...), the MR disables auto selection of first item in the dropdown suggestion menu, until at least a character has been typed.
This behavior change originated from #22058 and #23578 in which problems with the ":" special command were pointed out.
## Are there points in the code the reviewer needs to double check?
At lines +187 and +242 there were originally no sorters. Given what ``DefaultOptions.sorter`` does, I don't think it is a problem.
## Why was this MR needed?
To solve #22058 and #23578
## Does this MR meet the acceptance criteria?
- [X] [Changelog entry](https://docs.gitlab.com/ce/development/changelog.html) added
- [ ] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)
- [ ] API support added
- Tests
- [ ] Added for this feature/bug
- [X] All builds are passing
- [X] Conform by the [merge request performance guides](http://docs.gitlab.com/ce/development/merge_request_performance_guidelines.html)
- [X] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides)
- [X] Branch has no merge conflicts with `master` (if it does - rebase it please)
- [X] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)
## What are the relevant issue numbers?
Closes #22058 and #23578
See merge request !7129
|
