- 27 May, 2020 40 commits
-
-
Dmitry Gruzd authored
Currently the code search uses ngrams to allow searching for prefixes as well as full matches. This takes up a lot of storage and can be replaced with a prefix search. This change removes the usage of edgeNGram_filter from our index mappings.
-
Natalia Tepluhina authored
Assign alerts sidebar base See merge request gitlab-org/gitlab!32642
-
Evan Read authored
Create vale test for unresolved merge conflicts Closes #219168 See merge request gitlab-org/gitlab!33125
-
Marcel Amirault authored
-
James Lopez authored
Check valid confidence and severity level when parsing See merge request gitlab-org/gitlab!33050
-
Ash McKenzie authored
Introduce instrumentation for all Elasticsearch HTTP requests Closes #214279 See merge request gitlab-org/gitlab!32822
-
Kushal Pandya authored
Remove update function logic from List model See merge request gitlab-org/gitlab!31900
-
Marvin Karegyeya authored
-
Kushal Pandya authored
Remove moveIssue logic from list model See merge request gitlab-org/gitlab!32242
-
Marvin Karegyeya authored
-
Kushal Pandya authored
Remove findLabel logic from issue model See merge request gitlab-org/gitlab!32239
-
Marvin Karegyeya authored
-
Kushal Pandya authored
Remove temporary datepicker position fix as it is no longer required See merge request gitlab-org/gitlab!31836
-
Stan Hu authored
Externally installed helm dependency See merge request gitlab-org/gitlab!32935
-
Kushal Pandya authored
Add context menu links to metrics dashboard panel Closes #215497 See merge request gitlab-org/gitlab!32646
-
Miguel Rincon authored
This change allows the user to define "links" in their panel definition to see them displayed next to their chart as a quick action to visit other pages.
-
Kushal Pandya authored
Alert table mobile hotfix See merge request gitlab-org/gitlab!33047
-
David O'Regan authored
-
Kushal Pandya authored
Remove removeissue logic to from list model See merge request gitlab-org/gitlab!32249
-
Marvin Karegyeya authored
-
Kushal Pandya authored
Remove findIssue logic from list model See merge request gitlab-org/gitlab!32241
-
Marvin Karegyeya authored
-
Kushal Pandya authored
Remove newIssue function logic from list model See merge request gitlab-org/gitlab!32244
-
Kushal Pandya authored
Remove addAssignees logic from issues model See merge request gitlab-org/gitlab!32231
-
Marvin Karegyeya authored
-
Heinrich Lee Yu authored
Remove LSIF API endpoints which aren't used See merge request gitlab-org/gitlab!32325
-
Heinrich Lee Yu authored
Add Kubernetes::NetworkPolicy#autodevops? See merge request gitlab-org/gitlab!32715
-
Dylan Griffith authored
This introduces the same pattern of instrumentation [we use for Redis](https://gitlab.com/gitlab-org/gitlab/-/blob/b16db2726d7b429d740ef3642dda13b528fc4fda/lib/gitlab/instrumentation/redis.rb). This MR also adds the instrumentation details to sidekiq logs like we do with Redis. This instruments at the lowest level by instrumenting the elasticsearch-transport gem which is used by the elasticsearch-rails gem and elasticsearch-api gem which are the higher level abstractions used by GitLab. This has been tested to log requests coming from both places. Other options considered for this solution involved following a similar pattern to https://github.com/elastic/elasticsearch-rails/blob/1c3226d8186af6e8446fa5091f5b27760c29f896/elasticsearch-rails/lib/elasticsearch/rails/instrumentation/log_subscriber.rb which would extend the log subscriber pattern to be more than just searches in the context of the elasticsearch-rails gem but this seemed more convoluted than the approach I took since it requires monkey patching to publish a message then a separate class to subscribe and store those messages and so the pattern didn't seem to be beneficial unless you plan to have multiple subscribers. Additionally I considered using Faraday middleware to track this since the Elasticsearch gem uses Faraday by default but again I opted not to do that since it seemed trickier to manipulate the client config following https://github.com/elastic/elasticsearch-ruby/tree/master/elasticsearch-transport#transport-implementations and implement the required middleware etc. than just prepending the method following the same pattern as Redis.
-
Tiger Watson authored
Create operations_feature_flags_issues Table See merge request gitlab-org/gitlab!32876
-
Jason Goodman authored
For linking feature flags and issues
-
Heinrich Lee Yu authored
Fix Merge Request Note Label URLs See merge request gitlab-org/gitlab!30428
-
Lee Tickett authored
-
Heinrich Lee Yu authored
Standardize template names See merge request gitlab-org/gitlab!32612
-
Ben Bodenmiller authored
-
Igor Drozdov authored
Infer merge request in Discussions::ResolveService See merge request gitlab-org/gitlab!32932
-
Shaun McCann authored
Docs - how to get license details via Rails console See merge request gitlab-org/gitlab!33123
-
Thong Kuah authored
Merge branch '219193-foss-job-failure-with-unintialized-constant-uninitialized-constant-gitlab-throttle-in-spec' into 'master' Remove `/config/initializers/rack_attack.rb` from `.gitignore` Closes #219193 See merge request gitlab-org/gitlab!33128
-
Igor Drozdov authored
We used them for the first code intelligence iteration Now we don't need them, so we can remove
-
Albert Salim authored
-
Evan Read authored
Add docs for the PostHog cluster application See merge request gitlab-org/gitlab!29152
-