* `duo_features_enabled` was already an attribute on the
  `project_settings` table
* This MR uses the cascading settings framework to add this attribute to
  the `namespace_settings` table as well: https://docs.gitlab.com/ee/development/cascading_settings.html
* Other cascading settings assume that projects inherit the setting
  value from their parent group. For this setting, we want each project
  to be able to have a distinct setting value that may be different from
  its parent group. To do this, a new `CascadingProjectSettingAttribute`
  module was added that has very similar functionality to the
  `CascadingNamespaceSettingsAttribute` module.
* THis MR adds the cascading setting and behavior but the setting will
  not affect Duo Chat or Code Suggestions settings until a follow-on MR.
* #441481

Changelog: added
EE: true

Changelog: fixed

Changelog: removed

jitsu_key column is no longer used and this commit adds an ignore rule.

Allen Cook authored 1 year ago and Dylan Griffith committed 1 year ago

Changelog: deprecated

Kassio Borges authored 1 year ago and GitLab Release Tools Bot committed 1 year ago

Merge branch 'security-validate-project-path-availability' into 'master'

See merge request gitlab-org/security/gitlab!3388

Changelog: security

Add an ignore_column command to the emails_disabled field of the
projects table and convert usages to  using emails_enabled.

Update frontend descriptions and find places where emails_disabled
is set directly.

Changelog: added
EE: true

Allen Cook authored 1 year ago and Sincheol (David) Kim committed 1 year ago

Changelog: added

Allen Cook authored 1 year ago and Jose Ivan Vargas committed 1 year ago

Changelog: added

Markus Ferrell authored 1 year ago and Max Woolf committed 1 year ago

Changelog: added

Kassio Borges authored 2 years ago and George Koltsov committed 2 years ago

This feature is behind a feature flag for now.

This allows the users to use a unique domain for the gitlab-pages.

Peter Leitzen authored 2 years ago and Drew Blessing committed 2 years ago

Replace "!" and "?" with their unicode counterparts.

Example:
  key? becomes key？
  key! becomes key！

Fix existing use of `strong_memoize_attr` with member name.

Before:
  strong_memoize_attr :enabled?, :enabled

After:
  strong_memoize_attr :enabled?

Kyle Edwards authored 2 years ago and Peter Leitzen committed 2 years ago

Fixes: #382053
Changelog: fixed

This commit changes the way in which
`Vulnerabilities::Statistics::ScheduleWorker` queries the database so
that we're not affected by the data distribution in the project table.

EE: true
Changelog: fixed

Igor Drozdov authored 2 years ago and Patrick Cyiza committed 2 years ago

- Allow specifying a template in the Project Settings UI
- When an MR is created from an issue, a branch name is generated
according to the configured template

Changelog: added

Reuben Pereira authored 2 years ago and Mayra Cabrera committed 2 years ago

Merge branch 'sync-security-with-canonical' into 'master'

See merge request gitlab-org/security/gitlab!2826

Changelog: security

Alper Akgun authored 2 years ago and Mikołaj Wawrzyniak committed 2 years ago

For applied machine learning feature for ultimate customers on
gitlab.com

Changelog: added

Joe Snyder authored 2 years ago and Kerri Miller committed 2 years ago

Add a column to both the project and the namespace settings which will
control whether a comment on a line in a merge request will show
the code section that goes with the comment.

Add necessary parts of "back end" code to utilize this column.
Front end will follow after this merge.

Changelog: added

Abdul Wadood authored 2 years ago and Ethan Urie committed 2 years ago

Also, update it in groups/transfer_service.rb where `update_all` is
used which results in skipping of callbacks.

This removes all `default_enabled: :yaml | true | false`

Eugie Limpin authored 2 years ago and Michael Kozono committed 2 years ago

Update Projects::RecordTargetPlatformsWorker to handle detection of
projects built for the Android platform. It executes a new service
(Projects::AndroidTargetPlatformDetectorService) to determine if a given
project that uses Java or Kotlin is an Android project by checking if
the file AndroidManifest.xml is present in the project repository.

Harsimar Sandhu authored 2 years ago and Aleksei Lipniagov committed 2 years ago

Changelog: added
EE: true

Eugie Limpin authored 2 years ago and Mayra Cabrera committed 2 years ago

Like repository language detection feature, we'll try to detect if a
project is built for Apple iOS platform. This information will be used
in experiments to customize the experience (e.g. suggest setting up a
MacOS runners) of developers involved in such projects.

This detection will happen every time changes are pushed to the
project’s main branch and after a project is imported (using a project
template when creating a project is also an import). Detection is
executed in the background as a Sidekiq job at most once every hour
(using ExclusiveLease) and only if the project uses Swift or Objective-C
programming language.

If the project is detected as built for iOS we mark it by setting the
project’s corresponding ProjectSetting `target_platforms` attribute to
[‘ios’].

Changelog: added

Changelog: added

Piotr Stankowski authored 3 years ago and Michael Kozono committed 3 years ago

This change allows us to simplify merge commit textarea placeholder,
which did not render new lines in Safari.

Changelog: changed

Kerri Miller authored 3 years ago and Mayra Cabrera committed 3 years ago

This reverts merge request !79229
Changelog: other

Closes #343909

Changelog: added

This commit adds squash_commit_template column in project_settings.
It also adds this field to project's model.

Piotr Stankowski authored 3 years ago and Piotr Stankowski committed 3 years ago

This commit adds merge_commit_template column in project_settings.
It also adds this field to project's model.

project_settings.allow_editing_commit_messages was ignored in 14.2 and
the column was removed in 14.3. Following the dropping column process,
the `ignore_column` statement can be removed in 14.4

Related to #336783

Adds a new field to project level settings
behind a default-off feature flag which will
eventually prevent the merging of a merge request
without an associated Jira issue.

Gary Holtz authored 4 years ago and Rémy Coutable committed 4 years ago

In particular this:

* Adds an enum to the project_settings model with squash defaults
* Adds logic to reject merges when they don't meet the criteria
* Adds specs for the above
* Adds some endpoints for the frontend work
* Adds specs for the above

Thanks to @enzuru for the awesome groundwork on this! A lot of the code
is taken from his initial MR:

https://gitlab.com/gitlab-org/git lab/-/merge_requests/27833