| Age | Commit message (Collapse) | Author |
|---|
|
Remove puts
Remove puts
|
|
Bump clair-local-scan to v2.0.8
See merge request gitlab-org/gitlab-ce!27977
|
|
|
|
CE Show disabled project repo mirrors
See merge request gitlab-org/gitlab-ce!27326
|
|
Quarantine login via oauth spec
See merge request gitlab-org/gitlab-ce!28176
|
|
remove note that multi-line suggestions are not yet available
See merge request gitlab-org/gitlab-ce!28119
|
|
|
|
Improve performance of the global search for issuables
Closes #59522
See merge request gitlab-org/gitlab-ce!27817
|
|
Removed the conditions added to
Project.with_feature_available_for_user, and moved to the
IssuableFinder. Now, we ensure that, in the projects retrieved
in the Finder, the user has enough access for the feature.
|
|
doc/ci: include local: remove superfluous ":"
See merge request gitlab-org/gitlab-ce!28112
|
|
Set created_at and updated_at for sorting specs
Closes #61541
See merge request gitlab-org/gitlab-ce!28173
|
|
Fix installation from source
See merge request gitlab-org/gitlab-ce!28170
|
|
Upgrade Gitaly to v1.42.0
See merge request gitlab-org/gitlab-ce!28135
|
|
|
|
CE Backport for Dependency Proxy UI
See merge request gitlab-org/gitlab-ce!27965
|
|
Clean up CarrierWave's import/export files
Closes #60656
See merge request gitlab-org/gitlab-ce!27487
|
|
|
|
Add wbr style for IE11 compatibility
See merge request gitlab-org/gitlab-ce!27846
|
|
Unlike uploads that have been uploaded with Tempfile, the project
import/export archives are stored in a temporary cache directory and
remain there if:
1. Object storage is enabled
2. `move_to_store` is set to `true`.
CarrierWave will leave these files there until disk space runs out or a
clean step is run manually.
If `move_to_store` is set to `false`, CarrierWave will remove the files
after storing them. However, unlike a local file, with object storage,
the file is still copied, so setting `move_to_store` to `true`
doesn't buy us anything.
To ensure files are cleaned up, we can just inherit from the
GitlabUploader implementation of `move_to_store`, which returns `true`
if it's a local file, `false` otherwise.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/60656
|
|
This makes sure that the results are predictable and the same on both
Postgres and MySQL
|
|
Cleans up todos.scss style-lint warnings
Closes #59930
See merge request gitlab-org/gitlab-ce!28076
|
|
Generate EE-specific JavaScript fixtures into ee/ directory (CE-backport)
See merge request gitlab-org/gitlab-ce!28032
|
|
Only renders Next badge for gitlab.com
Closes #61278
See merge request gitlab-org/gitlab-ce!28056
|
|
|
|
Compiling git has a wrong symbol that leads into invalid command
|
|
Allow replying to an individual note in the API
Closes #61392
See merge request gitlab-org/gitlab-ce!28120
|
|
Strip whitespace for PipelineSchedule#cron
See merge request gitlab-org/gitlab-ce!27990
|
|
Instance level k8s clusters
See merge request gitlab-org/gitlab-ce!27196
|
|
Additional fix to handle NULL lock_version
See merge request gitlab-org/gitlab-ce!28153
|
|
Backport members SCSS changes
See merge request gitlab-org/gitlab-ce!28115
|
|
Resolve "Add filtering to project dashboard [FE]"
Closes #56992
See merge request gitlab-org/gitlab-ce!25231
|
|
Fix update head pipeline process of Pipelines for merge requests
See merge request gitlab-org/gitlab-ce!28057
|
|
If the UI sends a string value for lock_version (e.g. "0"), then the
previous monkey patch did not properly handle that properly. This
commit casts the value to an integer to determine whether to look for
NULL lock_versions.
For merge requests, GitLab sends a POST request to
`namespace/project/merge_requests/:iid` with the
`merge_request[lock_version]` parameter with a string `0`. The string
value comes from the form field, which explains why
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/28145 wasn't
sufficient.
|
|
Correct repo mirror SSH key generation docs
See merge request gitlab-org/gitlab-ce!27998
|
|
Show disabled mirrors with a badge so that they
can be deleted by project owners.
|
|
Add issue template for refactorings
See merge request gitlab-org/gitlab-ce!27889
|
|
CE Add leave link to access_granted email
See merge request gitlab-org/gitlab-ce!27892
|
|
(CE Port) New user onboarding (Welcome screen)
See merge request gitlab-org/gitlab-ce!28062
|
|
- Add styles for blue popovers
- Add render_if_exists to help menu for "Learn GitLab" menu item
|
|
Resolve "Support Prometheus for group-level clusters"
Closes #51963
See merge request gitlab-org/gitlab-ce!27280
|
|
|
|
[CE] Compute resolver complexity based on items
See merge request gitlab-org/gitlab-ce!28017
|
|
If a field is a resolver, its complexity is automatically
increased. By default we add extra points for sort and search
arguments (which will be common for various resolvers).
For specific resolvers we add field-specific complexity, e.g.
for Issues complexity is increased if we filter issues by `labelName`
(because then SQL query is more complex). We may want to tune these
values in future depending on real-life results.
Complexity is also dependent on the number of loaded nodes, but only
if we don't search by specific ID(s). Also added complexity is limited
(by default only twice more than child complexity) - the reason is
that although it's more complex to process more items, the complexity
increase is not linear (there is not so much difference between loading
10, 20 or 100 records from DB).
|
|
|
|
|
|
|
|
|
|
Try to simplify feature flag checks by using policies
|
|
There are two cluster hierarchies one for the deployment platform and
one for controllers. The main difference is that deployment platforms do
not check user permissions and only return the first match.
|
|
Instance level clusters were already mostly supported, this change adds
admin area controllers for cluster CRUD
|
