- 18 Jun, 2019 40 commits
-
-
GitLab Bot authored
-
Kamil Trzciński authored
#57815 Changes for UltraAuth users See merge request gitlab-org/gitlab-ce!28941
-
Kartikey Tanna authored
Disabled password authentication for the users registered using omniauth-ultraauth strategy
-
GitLab Bot authored
-
Fatih Acet authored
Fix empty security dashboard props See merge request gitlab-org/gitlab-ee!14186
-
Mike Greiling authored
Update dependency @gitlab/ui to ^4.3.0 See merge request gitlab-org/gitlab-ce!29800
-
GitLab Bot authored
-
Lin Jen-Shin authored
Use new Code Quality job definition in Auto DevOps See merge request gitlab-org/gitlab-ce!29475
-
GitLab Bot authored
-
Rémy Coutable authored
Look for new branches more carefully Closes #59257 See merge request gitlab-org/gitlab-ce!29761
-
Paul Gascou-Vaillancourt authored
-
GitLab Bot authored
-
Mike Greiling authored
Rename TOKEN_TYPES to USER_TOKEN_TYPES See merge request gitlab-org/gitlab-ce!29785
-
Mike Greiling authored
Rename TOKEN_TYPES to USER_TOKEN_TYPES Closes #12237 See merge request gitlab-org/gitlab-ee!14209
-
Arun Kumar Mohan authored
-
Sean McGivern authored
Merge branch '12249-broken-master-group-routing-routing-legacy-redirection-multiple-redirects-redirects-when-the-nested-group-does-not-exist' into 'master' Resolve "Broken master: Group routing routing legacy redirection multiple redirects redirects when the nested group does not exist" Closes #12249 See merge request gitlab-org/gitlab-ee!14255
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
GitLab Bot authored
-
Sean McGivern authored
Move some quick actions feature specs to unit tests Closes #60515 See merge request gitlab-org/gitlab-ce!28795
-
Felipe Artur authored
Move some feature specs for issues/merge requests quick actions to unit tests. They are taking too long to run on the pipelines.
-
Sean McGivern authored
Move some quick actions feature specs to unit tests See merge request gitlab-org/gitlab-ee!14124
-
Felipe Artur authored
Move some feature specs for issues/merge requests quick actions to unit tests. They are taking too long to run on the pipelines.
-
null authored
-
Yorick Peterse authored
Move approval MR rule report_type migration CE See merge request gitlab-org/gitlab-ee!14189
-
Yorick Peterse authored
Backport approval MR rules report_type migration to CE See merge request gitlab-org/gitlab-ce!29766
-
GitLab Bot authored
-
Kamil Trzciński authored
Add migrations needed to encrypt feature flags client tokens See merge request gitlab-org/gitlab-ce!29320
-
Kamil Trzciński authored
Encrypt feature flags client tokens See merge request gitlab-org/gitlab-ee!14021
-
Lucas Charles authored
-
GitLab Bot authored
-
Douwe Maan authored
Feature flag default on catfile cache Closes gitaly#1712 See merge request gitlab-org/gitlab-ce!29556
-
Achilleas Pipinellis authored
Https many links in docs See merge request gitlab-org/gitlab-ce!29776
-
Evan Read authored
-
GitLab Bot authored
-
Achilleas Pipinellis authored
Update list items to conform to documentation style guide See merge request gitlab-org/gitlab-ce!29739
-
Nick Thomas authored
In certain cases, GitLab can miss a PostReceive invocation the first time a branch is pushed. When this happens, the "branch created" hooks are not run, which means various features don't work until the branch is deleted and pushed again. This MR changes the `Git::BranchPushService` so it checks the cache of existing branches in addition to the `oldrev` reported for the branch. If the branch name isn't in the cache, chances are we haven't run the service yet (it's what refreshes the cache), so we can go ahead and run it, even through `oldrev` is set. If the cache has been cleared by some other means in the meantime, then we'll still fail to run the hooks when we should. Fixing that in the general case is a larger problem, and we'd need to devote significant engineering effort to it. There's a chance that we'll run the relevant hooks *multiple times* with this change, if there's a race between the branch being created, and the `PostReceive` worker being run multiple times, but this can already happen, since Sidekiq is "at-least-once" execution of jobs. So, this should be safe.
-
Grzegorz Bizon authored
Remove deprecated group routes See merge request gitlab-org/gitlab-ce!29351
-
Yorick Peterse authored
Upgrade Gitaly to v1.47.0 See merge request gitlab-org/gitlab-ce!29789
-
GitalyBot authored
-
Achilleas Pipinellis authored
Fix typos, grammar and wording for SAST and DS report JSON docs See merge request gitlab-org/gitlab-ce!29744
-