| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Hide group control nav if no options present
## What does this MR do?
Hides the group nav controls if no options present in the dropdown.
Also fixed the alignment of the dropdown to match the project page.
## What are the relevant issue numbers?
Closes #19120
See merge request !5155
|
|
|
|
'gh-importer-use-default-project-visibility-for-non-private-projects' into 'master'
GitHub importer use default project visibility for non-private projects
## What does this MR do?
GitHub importer use the `Default Project Visibility` setting for all non-private projects.
## Why was this MR needed?
This allow users to import projects when `Public` visibility is restricted.
## What are the relevant issue numbers?
Fixes #21437
See merge request !6023
|
|
|
|
|
|
Refactor ability.rb into Policies
## What does this MR do?
Factors out `ability.rb` into a new abstraction - the "policy" (stored in `app/policies`). A policy is a class named `#{class_name}Policy` (looked up automatically as needed) that implements `rules` as follows:
``` ruby
class ThingPolicy < BasePolicy
def rules
@user # this is a user to determine abilities for, optionally nil in the anonymous case
@subject # this is the subject of the ability, guaranteed to be an instance of `Thing`
can! :some_ability # grant the :some_ability permission
cannot! :some_ability # ensure that :some_ability is not allowed. this overrides any `can!` that is called before or after
delegate! @subject.other_thing # merge the abilities (can!) and prohibitions (cannot!) from `@subject.other_thing`
can? :some_ability # test whether, so far, :some_ability is allowed
end
def anonymous_rules
# optional. if not implemented `rules` is called where `@user` is nil. otherwise this method is called when `@user` is nil.
end
end
```
See merge request !5796
|
|
Add a BroadcastMessage API
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/21628
See merge request !6112
|
|
Fix bug where pagination is still displayed despite all todos marked as done
## What does this MR do?
Changes the todo `mark all as done` button callback to remove pagination and add user friendly text `"You're all done!"` so that it is consistent with what the page should look like after refreshing
## Are there points in the code the reviewer needs to double check?
Shouldn't be
## Why was this MR needed?
Resolve existing UI inconsistency
## 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
- Tests
- [x] Added for this feature/bug
- [x] All builds are passing
- [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 #21048
See merge request !6113
|
|
Check for existance of elements under test in application_spec.js
## What does this MR do?
Checks that the elements under test in `application_spec.js` actually exist.
## Why was this MR needed?
```
$ echo 'just garbage' > spec/javascripts/fixtures/application.html.haml
$ bundle exec teaspoon spec/javascripts/application_spec.js
2 examples, 0 failures
```
See merge request !6051
|
|
Fixed escaping issue with labels filter
## What does this MR do?
Encodes label names to stop any JS errors.
## What are the relevant issue numbers?
Closes #15552
See merge request !6123
|
|
|
|
|
|
Remove redundant js-timeago-pending from user activity log
## What does this MR do?
Enables the `skip_js` feature of `time_ago_with_tooltip()` since the frontend was already re-initializing `timeago` on all the elements after it received the data from the backend.
## Are there points in the code the reviewer needs to double check?
Shouldn't be
## Why was this MR needed?
* Reduces bandwidth usage (Reduced by ~3.1kb)
* Removes redundant code
* Happy DOM :balloon:
## What are the relevant issue numbers?
Closes #21063
## Screenshots (if relevant)
Before (DOM):
After (DOM):
Before (Bandwidth):
After (Bandwidth):
## Does this MR meet the acceptance criteria?
- [x] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added
- Tests
- [x] All builds are passing
- [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)
See merge request !5871
|
|
Filters tags by name
Closes #21673
See merge request !6121
|
|
'21567-fix-sorting-issues-by-last-updated-after-import-from-github' into 'master'
Fix sorting issues by "last updated" after import from GitHub
## What does this MR do?
Don't touch Issue/Merge Request when importing GitHub comments as it will trigger an update on `updated_at` field. It also use `updated_at` as the last updated date doesn't matter the Issue/Pull Request state.
## Why was this MR needed?
After import from GitHub, sorting issues by "last updated" doesn't work as expected.
## What are the relevant issue numbers?
Fixes #21567
See merge request !6110
|
|
Fix toggler_behavior.js to toggle ajax loaded contents like `diffs` page.
## What does this MR do?
Fix toggle in diffs
## What are the relevant issue numbers?
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/21676, https://gitlab.com/gitlab-org/gitlab-ce/issues/21686.
See merge request !6119
|
|
Fixed invisible scroll controlls on build page on iPhone
## What does this MR do?
Fixes invisible scroll controls on build page on iPhone
## Are there points in the code the reviewer needs to double check?
No.
## Why was this MR needed?
Because it's not correct behavior.
## 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
- [ ] 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?
Not found
See merge request !6125
|
|
|
|
Fix Sentry not reporting right program for Sidekiq workers
Moves program tag into the global configuration since this doesn't change and since Sidekiq workers get a unique context for each event.
Closes #21410
See merge request !6004
|
|
Fix wording in PROCESS.md
Simple grammar fix (those issue -> those issues)
See merge request !6131
|
|
|
|
|
|
|
|
|
|
|
|
Fix repo title alignment
## What does this MR do?
Adds an extra pixel margin to the hamburger button so that it matches the baseline of the repo title
## Are there points in the code the reviewer needs to double check?
Shouldn't be any :smile:
## Why was this MR needed?
Resolve UI Inconsistency
## What are the relevant issue numbers?
Closes #21408
## 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
- Tests
- [x] All builds are passing
- [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)
See merge request !6046
|
|
Block concurrent pipeline processings
## What does this MR do?
It's possible that two builds that succeed at the same will try to
concurrently process pipeline. This can lead to scenario when it will
fail to trigger next stages.
This MR makes sure that process of updating is blocking.
Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/21263
See merge request !6090
|
|
API: Expose issue confidentiality flag.
## What does this MR do?
This MR adds support for confidential issues the the API. The property as exposed and users can create or update confidential issues.
## What are the relevant issue numbers?
Closes #17199
See merge request !5384
|
|
The ID of a project can be also a string
## What does this MR do?
Add the integer type for the project's ID in the API docs.
## What are the relevant issue numbers?
Missed a few spots in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6102
See merge request !6133
|
|
[ci skip]
|
|
|
|
Minor code refactor for inlining functions in logo JS.
See merge request !6097
|
|
|
|
|
|
Create bitmaps during 'git gc'
## What does this MR do?
Add instructions to enable creation of Git packfile bitmaps.
## Why was this MR needed?
Because we still are not using Git packfile bitmaps in GitLab
[ci skip]
See merge request !6104
|
|
|
|
|
|
Don't expose a user's private token in the `/api/v3/user` API
## Why was this MR needed?
A user's private token is being leaked in the `/api/v3/user` API.
## What are the relevant issue numbers?
- Closes #20911
## Does this MR meet the acceptance criteria?
- [ ] #20911 !6047 Application-Specific Tokens Are Insecure
- [x] Implementation
- [x] Test
- [x] CHANGELOG
- [x] Make sure build is green
- [x] Assign to endboss
- [ ] Wait for merge
See merge request !6047
|
|
Fixes #20456.
|
|
Allow setting branch refs for MR
@dbalexandre can you take a look please?
See merge request !6025
|
|
|
|
We rarely use Russian-doll caching in views, and when we do, it's
typically with a naturally-invalidating key. In the case of the commit
partial, though, the author lookup isn't part of the cache key - because
we're not going to use the state of the users table - and so a new email
address can take up to two weeks to show against the commits list.
Limiting this to a day still caches the partial for a healthy amount of
time, without as bad a worst case scenario.
|
|
Added performance guidelines for new MRs
## What does this MR do?
This MR adds a set of guides that should be followed by merge request authors.
## Are there points in the code the reviewer needs to double check?
Spelling, grammar, etc
## Why was this MR needed?
There is no set of guidelines one should follow when submitting merge requests. This leads to developers at times disregarding performance. This in turn results in performance specialists having to clean up the mess, or production engineers being woken up in the middle of the night because the database is on fire.
## Does this MR meet the acceptance criteria?
- [x] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)
- Tests
- [x] All builds are passing
- [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)
cc @DouweM @rspeicher @pcarranza @dzaporozhets
See merge request !5905
|
|
|
|
Remove redundant pipeline tooltips from short labels
## What does this MR do?
Removes the tooltips from labels that have less than 12 characters, so that the tooltips only show when the pipeline labels are truncated
## Are there points in the code the reviewer needs to double check?
None
## Why was this MR needed?
Removes unnecessary tooltips for non-truncated pipeline labels
## 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
- Tests
- [x] All builds are passing
- [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?
#21542
See merge request !6058
|
|
|
|
Closes #15552
|
|
Only visible when scrollable area is larger than height
|
