- 12 Aug, 2021 40 commits
-
-
Piotr Skorupa authored
-
Enrique Alcántara authored
Fix css on markdown toolbar header See merge request gitlab-org/gitlab!68062
-
Alper Akgun authored
Add instrumentation_class to quickactions event metrics See merge request gitlab-org/gitlab!67716
-
Patrick Bair authored
Denormalize `ci_builds` columns into `security_scans` See merge request gitlab-org/gitlab!66963
-
Olena Horal-Koretska authored
Add/remove space and tab See merge request gitlab-org/gitlab!67747
-
scootergrisen authored
-
Mayra Cabrera authored
Hidden issues See merge request gitlab-org/gitlab!66687
-
Mayra Cabrera authored
Quarantine cluster_health_dashboard_spec See merge request gitlab-org/gitlab!68066
-
Nikola Milojevic authored
Accept both uppercase and lowercase for data_category in metric definition See merge request gitlab-org/gitlab!67469
-
Steve Abrams authored
Implement override_uuids! for Security Reports See merge request gitlab-org/gitlab!66978
-
rossfuhrman authored
-
Andrew Fontaine authored
Add environments survey alert See merge request gitlab-org/gitlab!67243
-
Nick Gaskill authored
Fix typo in graphql documentation for packages See merge request gitlab-org/gitlab!68038
-
Michael Lunøe authored
Fix copy on Successful Purchase Banner See merge request gitlab-org/gitlab!67947
-
Kyle Wiebers authored
Relates to https://gitlab.com/gitlab-org/gitlab/-/issues/338341
-
Daniel Fosco authored
Changelog: fixed
-
Max Woolf authored
Update feature flags links for new queuing system See merge request gitlab-org/gitlab!68012
-
Jarek Ostrowski authored
-
Simon Knox authored
Update Pikaday colors for dark mode See merge request gitlab-org/gitlab!65247
-
Tetiana Chupryna authored
Report to Sentry for long Redis durations See merge request gitlab-org/gitlab!67512
-
Brandon Labuschagne authored
Moved Source Editor's theming into utilities See merge request gitlab-org/gitlab!67916
-
Denys Mishunov authored
-
Vitali Tatarintev authored
Fix expired artifacts causing dependency failures on locked pipelines See merge request gitlab-org/gitlab!67764
-
Keith Richardson authored
-
Phil Hughes authored
Merge branch '323245-provide-terraform-backend-environment-variables-in-operations-terraform-ui' into 'master' Provide Terraform backend environment variables in Operations-->Terraform UI See merge request gitlab-org/gitlab!67417
-
Anna Vovchenko authored
-
Natalia Tepluhina authored
Finalise package details refactor See merge request gitlab-org/gitlab!67991
-
Nicolò Maria Mezzopera authored
-
Dmitriy Zaporozhets (DZ) authored
Raise error when using invalid relation type in member finder See merge request gitlab-org/gitlab!67849
-
Martin Wortschack authored
Updated reporting period message on DevOps Adoption Report See merge request gitlab-org/gitlab!68034
-
Bob Van Landuyt authored
checks: Fix combinatorial explosion in `#commits_for()` See merge request gitlab-org/gitlab!67827
-
Thong Kuah authored
Revert "Merge branch '337719-linear-project-ancestors' into 'master'" See merge request gitlab-org/gitlab!68051
-
Markus Koller authored
Change Feature Flag group::ecosystem to group::integrations See merge request gitlab-org/gitlab!67963
-
Patrick Steinhardt authored
The function `#commits_for()` has been introduced via 156ce433 (checks: Implement infrastructure for bulk diff checks, 2021-07-29) in order to allow bulk-loading of commits. What this function does is given a set of new commits and a specific object ID, it will do a graph walk of these new commits starting from this ID in order to extract only those commits which have been newly introduced via this object ID. As it turns out though, the implementation has a bug which causes combinatorial explosion: if a commit is reachable via multiple commits, then it will be walked and returned multiple times. This can happen if there are merge commits, where we'll now repeatedly walk all common ancestors of both commits. In case these again contain merge commits, the common ancestors again get walked multiple times. The result is that commits get walked exponentially many times. For the following graph with criss-cross merges, this causes us to return 768 commits instead of the expected 18: o---o---o---o---o---o---o---o / \ / \ / \ / \ / \ / \ / \ / \ o X X X X X X X o \ / \ / \ / \ / \ / \ / \ / \ / o---o---o---o---o---o---o---o Fix the bug by removing seen commit IDs from the hash tracking commits by their object ID. Furthermore, the pending queue is converted to a set such that we don't re-add IDs which we have already seen before such that it doesn't exhibit exponential growth. Changelog: fixed
-
Marcin Sedlak-Jakubowski authored
Set 36h limit for reviewer to respond when at capacity See merge request gitlab-org/gitlab!67481
-
Matthias Käppler authored
-
Heinrich Lee Yu authored
This reverts merge request !67565
-
Raimund Hook authored
Message now more clearly shows that the update is automatic at the beginning of the month, and reflects the previous calendar month. Fixes https://gitlab.com/gitlab-org/gitlab/-/issues/335640 Changelog: changed EE: true Signed-off-by: Raimund Hook <raimund.hook@exfo.com>
-
Alper Akgun authored
Add performance_indicator_type metric See merge request gitlab-org/gitlab!68043
-
Rajendra Kadam authored
-