Fixes bug on the Usage trends page in which the tooltips in the
Total projects & groups, Pipelines and Issues & Merge Requests charts
are empty upon fetching paginated data

Changelog: fixed

Changelog: fixed

Since the `disable_git_http_fetch_writes` FF does not define
a feature flag actor, it is currently not possible to increment
the fetch project statistics without enabling or disabling it
for all projects.

This commit introduces the `allow_git_http_fetch_writes` FF
that allow us to control this and unskip the statistics
for specific projects.

Changelog: changed

Coung Ngo 创作于 8 months ago ，Stanislav Lashmanov 提交于 8 months ago

Adds confidential, group, and my-reaction filters

Behind feature flags
- work_item_epics
- work_item_epics_rollout
- namespace_level_work_items

Changelog: changed

## What does this MR do and why?

Add and backfill project_id for evidences.

This table has a
[desired sharding key](https://docs.gitlab.com/ee/development/database/multiple_databases.html#define-a-desired_sharding_key-to-automatically-backfill-a-sharding_key)
configured ([view configuration](https://gitlab.com/gitlab-org/gitlab/-/blob/master/db/docs/evidences.yml)).

This merge request is the first step towards transforming the desired sharding key into a
[sharding key](https://docs.gitlab.com/ee/development/database/multiple_databases.html#defining-a-sharding-key-for-all-cell-local-tables).

This involves three changes:

- Adding a new column that will serve as the sharding key (along with the relevant index and foreign key).
- Populating the sharding key when new records are created by adding a database function and trigger.
- Scheduling a [batched background migration](https://docs.gitlab.com/ee/development/database/batched_background_migrations.html)
  to set the sharding key for existing records.

Once the background migration has completed, a second merge request will be created to finalize the background
migration and validate the not null constraint.

## How to verify

We have assigned a random backend engineer from ~"group::compliance" to review these changes. Please review this merge
request from a ~backend perspective. The main thing we are looking to verify is that the added column and association
match the values specified by the [desired sharding key](https://gitlab.com/gitlab-org/gitlab/-/blob/master/db/docs/evidences.yml)
configuration and that backfilling the column from this other table makes sense in the context of this feature.

When you are finished, please:

1. Trigger the [database testing pipeline](https://docs.gitlab.com/ee/development/database/database_migration_pipeline.html)
   as instructed by Danger.
1. Request a review from the ~backend maintainer and ~database reviewer suggested by Danger.

If you have any questions or concerns, reach out to `@tigerwnz` or @manojmj.

This merge request was generated by a once off keep implemented in
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/143774

This change was generated by
[gitlab-housekeeper](https://gitlab.com/gitlab-org/gitlab/-/tree/master/gems/gitlab-housekeeper)
using the Keeps::BackfillDesiredShardingKeySmallTable keep.

To provide feedback on your experience with `gitlab-housekeeper` please comment in
<https://gitlab.com/gitlab-org/gitlab/-/issues/442003>.

Changelog: other

GraphQL filters out the SAML groups where the current user
is a member and the SAML session has expired because the
`needs_new_sso_session` condition in EE::GroupPolicy evaluates to true
for expired SAML sessions which in turn makes the `read_group` policy to
evaluate to false. This results in GraphQL returning less groups than
queried.

Here we filter out the inactive SAML session groups from the database
itself and return the expected number of groups requested by GraphQL
query.

Removes duplicate projects from the list when
selecting the project a child item should be
created in. If a project is in the 'Recently used'
group in the list, it will not appear in the
'Projects' group

Changelog: fixed

Initially we assumed that auto closing issues via merge request
was enabled for issues that exist at the group level. Now we
want to default to disabled if an issue exists at the group
level. In the future, we could add a setting to groups to add
the auto close feature. Better this way, as the other way, there's
no way to disable it.

Changelog: changed

Co-authored-by: Terri Chu <tchu@gitlab.com>

Click Flux sync badge to view resource details in a drawer.

Changelog: added

This change migrates the new UI
to use Vue Router rather than
direct url manipulation.

We track generic include file load times in the
`config_file_fetch_content_hash` metric. However, we might introduce a
feature that would increase the load times specifically when loading
components, so we need a metric that only tracks component content load
times.

Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/438275?work_item_iid=471843

Adds support for creating metric definitions with filters
defined when using the Internal Events CLI.

Changelog: fixed

`window.open` could cause cross-site leaks. We have a utility function,
`visitUrl`, which detects if a URL is external or internal and offers
protection against those leaks.

We enable a new eslint rule to discourage `window.open` and promote the
use of `visitUrl`.

This change set emits two new audit events: one when a new cluster agent
is created and one when a cluster agent is deleted or attempts of the
two.

Closes https://gitlab.com/gitlab-org/gitlab/-/issues/462749

Changelog: added
Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/462749
EE: true
MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/159593

Changelog: changed

- include concerns that can be reused
- implement methods and classes for Discussion
- add specs
- add adding type to notes migration

Changelog: other

Update tags_page and resolver to only check API
support vs checking Gitlab.com

Changelog: changed

- needed to remove lazy creation of user_details
- background migration to go over users table and
  find users w/o the needed entries and create them.

Changelog: other

Co-authored-by: David Fernandez <dfernandez@gitlab.com>

Usually if there are system notes that reference an item that
cannot be accessed by the user we filter out that system note
altogether.

This was not happening for system notes about adding or removing
a child work item or a parent work item.

Co-authored-by: Luke Duncalfe <lduncalfe@gitlab.com>

When publishing a npm package that its archive has been bundled with a custom root folder name, an error is raised stating that package.json not found. In this MR, we fix that by validating the archive as long as it has package.json file in its root regardless of the root folder name.

Changelog: fixed

This reverts merge request !158881

Introduces the Ci::Tagging model to replace
the ActsAsTaggableOn::Tagging model.

Signed-off-by: Rémy Coutable <remy@rymai.me>

- Update copy of show page and HTML / text emails.
- Use CardComponent for UI.

Changelog: changed

Remove flag references in code

Changelog: fixed
MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/160190

Changelog: fixed

Introduces the Ci::tag model which implements
the API needed by ActsAsTaggableOn::Tag to tag
jobs.