| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Fix typos in comments and specs
See merge request gitlab-org/gitlab-ce!22683
|
|
|
|
|
|
|
|
Remove EE-specific code from 'Discussion' models
See merge request gitlab-org/gitlab-ce!22687
|
|
Extract language_from_git_attributes as a concern so it can
ben included in two blob classes.
|
|
|
|
[master] Redact unsubscribe links in issuable texts
See merge request gitlab/gitlabhq!2528
|
|
|
|
Even though we currently only should have one group for a cluster, we
allow the flexibility to associate to other groups in the future.
This also matches the runner <=> groups association.
- Adds Cluster#first_group, aliased to Cluster#group. For the
conceivable future, a cluster will have at most one group.
- Prevent mixing of group and project clusters. If project type
clusters, it should only have projects assigned. Similarly with groups.
- Default cluster_type to :project_type. As it's very small table we can
set default and null: false in one release.
|
|
|
|
It's possible that user pastes accidentally also unsubscribe link
which is included in footer of notification emails. This unsubscribe
link contains personal token which attacker then use to act as the
original user (e.g. for sending comments under his/her identity).
|
|
|
|
This saves about 128 MB of baseline RAM usage per Unicorn and
Sidekiq process (!).
Linguist wasn't detecting languages anymore from CE/EE since
9ae8b57467ac8b38f1fa9020a466d94a93cbb9dd. However, Linguist::BlobHelper
was still being depended on by BlobLike and others.
This removes the Linguist gem, given it isn't required anymore.
EscapeUtils were pulled in as dependency, but given Banzai depends on
it, it is now added explicitly.
Previously, Linguist was used to detect the best ACE mode. Instead,
we rely on ACE to guess the best mode based on the file extension.
|
|
|
|
Backport CE changes from draft_notes addition in EE
See merge request gitlab-org/gitlab-ce!22125
|
|
Allows to filter issues by `Any milestone` in the API
Closes #51748
See merge request gitlab-org/gitlab-ce!22080
|
|
|
|
|
|
|
|
In GET `api/v4/projects/:id/issues` the user can filter issues
that have an assigned milestone through the parameter
`milestone=Any+Milestone`.
|
|
the earlier step
|
|
|
|
|
|
|
|
|
|
commit 9d9594ba20097dc4598f7eb42a9f9d78d73eae54
Author: Shinya Maeda <shinya@gitlab.com>
Date: Thu Sep 13 20:18:31 2018 +0900
Cancel scheduled jobs
commit f31c7172e07a9eb03b58c1e62eaa18cda4064aa6
Author: Shinya Maeda <shinya@gitlab.com>
Date: Thu Sep 13 11:18:42 2018 +0900
Add Ci::BuildSchedule
commit fb6b3ca638f40f9e1ee38b1fdd892bda4f6fede7
Author: Shinya Maeda <shinya@gitlab.com>
Date: Wed Sep 12 20:02:50 2018 +0900
Scheduled jobs
|
|
When a user cannot be renamed due to existing container registry tags, log the
namespace and an example project that has tags.
|
|
Even if it doesn’t save lines of code, since people will tend to use
code they’ve seen. And `SafeRequestStore` is safer since you
don’t have to remember to check `RequestStore.active?`.
|
|
These are clear wins.
|
|
Remove EE-specific lines from Plan concerns
See merge request gitlab-org/gitlab-ce!21448
|
|
|
|
|
|
|
|
|
|
This commit adds the module `FromUnion`, which provides the class method
`from_union`. This simplifies the process of selecting data from the
result of a UNION, and reduces the likelihood of making mistakes. As a
result, instead of this:
union = Gitlab::SQL::Union.new([foo, bar])
Foo.from("(#{union.to_sql}) #{Foo.table_name}")
We can now write this instead:
Foo.from_union([foo, bar])
This commit also includes some changes to make this new setup work
properly. For example, a bug in Rails 4
(https://github.com/rails/rails/issues/24193) would break the use of
`from("sub-query-here").includes(:relation)` in certain cases. There was
also a CI query which appeared to repeat a lot of conditions from an
outer query on an inner query, which isn't necessary.
Finally, we include a RuboCop cop to ensure developers use this new
module, instead of using Gitlab::SQL::Union directly.
Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/51307
|
|
CE: Properly implement prepending for Concern
See merge request gitlab-org/gitlab-ce!21444
|
|
This is a mess... Using prepend will give a different ancestors
chain we're not expecting. To fix this we'll need to know what
exactly methods we want to use in each classes using this module.
|
|
Partially addresses #47424.
|
|
Resolve "Remove old storage logic from Import/Export"
Closes #51144, #50109, #48778, and #51079
See merge request gitlab-org/gitlab-ce!21409
|
|
|
|
Move project services log to a separate file
See merge request gitlab-org/gitlab-ce!21316
|
|
|
|
|
|
Updated docs, refactor import/export code
Fix AvatarUploader path issue
Fix project export upload webhook error
|
|
Port changes for CODEOWNERS to CE
See merge request gitlab-org/gitlab-ce!21309
|
|
This ports the changes for the CODEOWNERS feature to CE:
- It adds the CODEOWNERS file.
- It adds the mention of the `with-codeowners` branch in TestEnv
|
|
Filter web hooks by branch
See merge request gitlab-org/gitlab-ce!19513
|
|
|
