- 28 Mar, 2022 40 commits
-
-
Gary Holtz authored
-
Gary Holtz authored
-
Gary Holtz authored
Changelog: security
-
Kerri Miller authored
Merge branch 'morefice/ui-should-explain-if-no-junit-report-artifacts-are-available-to-populate-unit-test-report' into 'master' Render errors if test report artifacts are expired See merge request gitlab-org/gitlab!83113
-
Max Orefice authored
This commit exposes a new attribute to our TestSuiteEntity which will be used to determine when junit artifacts have expired when displaying TestCases.
-
Alper Akgun authored
Define class for logged_out_marketing_header experiment See merge request gitlab-org/gitlab!83714
-
Nikola Milojevic authored
Sleep between inserting batches of refreshes See merge request gitlab-org/gitlab!83622
-
Kushal Pandya authored
Update copy for DAST Profiles library page See merge request gitlab-org/gitlab!83375
-
Enrique Alcántara authored
Update Content Editor Packages See merge request gitlab-org/gitlab!82586
-
Frédéric Caplette authored
Adjust icons and button wording for license compliance See merge request gitlab-org/gitlab!83703
-
Markus Koller authored
Added read_usage_quotas ability to ProjectPolicy See merge request gitlab-org/gitlab!82396
-
Furkan Ayhan authored
Cleanup secret variables refactoring in variables builder See merge request gitlab-org/gitlab!83428
-
Andy Soiron authored
Cleanup api_kaminari_count_with_limit See merge request gitlab-org/gitlab!81084
-
Jaspreet Singh authored
Changelog: removed
-
Kerri Miller authored
FIPS SSH key configuration settings See merge request gitlab-org/gitlab!81917
-
Marius Bobin authored
Changelog: other
-
Matthias Käppler authored
Clean up code for invite_team_email experiment See merge request gitlab-org/gitlab!82799
-
Amy Qualls authored
Crosslink other rate limits for GitLab.com See merge request gitlab-org/gitlab!83615
-
Bob Van Landuyt authored
-
Natalia Tepluhina authored
Show description text for "Users in Subscription" card for Ultimate plans only See merge request gitlab-org/gitlab!81286
-
Vitaly Slobodin authored
Changelog: changed EE: true
-
Natalia Tepluhina authored
Migrate to GlAlert in Pages Domains form See merge request gitlab-org/gitlab!83694
-
Etienne Baqué authored
Raise exception when gitaly-backup could not be found See merge request gitlab-org/gitlab!83555
-
Furkan Ayhan authored
Update API doc to show correct return type See merge request gitlab-org/gitlab!81895
-
Pavel Shutsin authored
Period limit default Insights yaml See merge request gitlab-org/gitlab!83718
-
Dheeraj Joshi authored
-
Dheeraj Joshi authored
EE: true Changelog: changed
-
Frédéric Caplette authored
Add empty state for Instance OAuth app page See merge request gitlab-org/gitlab!83279
-
Matthias Käppler authored
Enqueuer job: fix the re enqueue See merge request gitlab-org/gitlab!83527
-
Pavel Shutsin authored
Fix PA for projects in nested groups See merge request gitlab-org/gitlab!83282
-
Pavel Shutsin authored
Fix artifacts content-type See merge request gitlab-org/gitlab!83515
-
Frédéric Caplette authored
Fix project permission toggle behavior See merge request gitlab-org/gitlab!83503
-
Lukas 'Eipi' Eipert authored
Problem: ``` Given that you are on public project When you disable a permission And enable it again Then the dropdown shows that you selected the last value on the list While the internal input has another value set. ``` This has to do with a quirky behavior where we replace the `value` and the `options` provided to the `<select>` inside of the ProjectFeatureSettings input component. Internally we used the `selected` attribute of the `<option>` elements to track which option was selected. That attribute is just for initial rendering though: > If present, this Boolean attribute indicates that the option is > initially selected. If the `<option>` element is the descendant of a > `<select>` element whose multiple attribute is not set, only one > single `<option>` of this `<select>` element may have the selected > attribute. This seems to be non-problematic if one never changes the options that are availabe for the specific select. The solution for this is to create a computed property with a getter and setter and use that computed property as a v-model for the internal select. Changelog: fixed
-
Frédéric Caplette authored
Fix project permission toggle behavior See merge request gitlab-org/gitlab!83503
-
Lukas 'Eipi' Eipert authored
Problem: ``` Given that you are on public project When you disable a permission And enable it again Then the dropdown shows that you selected the last value on the list While the internal input has another value set. ``` This has to do with a quirky behavior where we replace the `value` and the `options` provided to the `<select>` inside of the ProjectFeatureSettings input component. Internally we used the `selected` attribute of the `<option>` elements to track which option was selected. That attribute is just for initial rendering though: > If present, this Boolean attribute indicates that the option is > initially selected. If the `<option>` element is the descendant of a > `<select>` element whose multiple attribute is not set, only one > single `<option>` of this `<select>` element may have the selected > attribute. This seems to be non-problematic if one never changes the options that are availabe for the specific select. The solution for this is to create a computed property with a getter and setter and use that computed property as a v-model for the internal select. Changelog: fixed
-
Savas Vedova authored
Add Submit Vulnerability button to empty page See merge request gitlab-org/gitlab!83597
-
Savas Vedova authored
When the user has the necessary permissions, display a button to create a vulnerability manually.
-
Kerri Miller authored
Resolve "Follow-up from "Implement API to get single MR rule"" See merge request gitlab-org/gitlab!83501
-
Nikola Milojevic authored
Fixed crm db seed trying to seed non-root groups See merge request gitlab-org/gitlab!83462
-
Adam Hegyi authored
Clean up after fixing issue when admin changes email See merge request gitlab-org/gitlab!83185
-