This deprecates the `confidential` parameter for the Notes API in favour
of `internal`. This affects the GraphQL API, REST API, and internal
Notes creation API.

We also expose the `internal` attribute now for a `Note` and the
behaviour of `internal` and `confidential` is the same.

In the case of submitting a request to create a note with
`internal: true`, and `confidential: false`, `internal` overrules the
`confidential` parameter.

In a follow-up work, the remaining mentions of `confidential` in the
Services, Models, and Database column will be renamed.

Changelog: deprecated

Changelog: added

Allows fetching labels for work items

This first iteration of
https://gitlab.com/gitlab-org/gitlab/-/issues/369202 documents the
`feature_flag` property as being deprecated and that it should not be
used.

It renames the argument so that it's clear it's not to be used for new
items.

It also updates the developer docs to include advice for using flags
with schema items besides fields, and where the flag is used to toggle
behavior.

Changelog: added

Updating start or due date in an Issue or WorkItem will now
trigger a relatime update so you can fetch the updated dates

Changelog: added

Changelog: added

Allows updating of a work item's assignees

Allows setting a start and due date to work items
via the work item widget GraphQL API

Changelog: changed

Using lazy evaluation prevents clearing out data for tests

Allows to delete file upload in a project or group.

Changelog: added

This fixes API (REST and GraphQL) spec files

Merge branch 'security-crm-fix' into 'master'

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

Changelog: security

Return validation error when timeline event's note is blank
during update

Changelog: changed

There is a growing number of differences between the GraphQL
functionality for different variable types. Moving to an interface
pattern now will spare us from having to write a lot of specific logic
for checking the variable type

You can fetch start and due date for a work item
through the work item widget interface.

This is same as Issue's confidential field.

Changelog: fixed
EE: true

Project and group CI variables can have an environment scope defined
that determines the environments in which the variable can be used.
Instance variables do not have an environment scope, so the
`environment_scope` field will always return `nil` for them.

Changelog: added

This field returns the variables given to a manual job when it is
played.

Changelog: added

This change adds a new GraphQL field: Pipeline.jobs(retried: Boolean)

This allows client to request retried, latest or all jobs.

This commit introduces a GraphQL Mutation allowing
a once-off toggle of the "onboarding_complete"
property in Pages metadata.

This commit introduces the frontend for an onboarding view for Pages
that will enable the user to configure their .gitlab-ci.yml file
directly in the UI.
This commit needs a follow up MR to be displayed by the UI.

This is all this does

This is needed to render the invite modal within the assignees widget

This is to allow showing historical status on releases in the UI, as
well as easily allow API consumers to see if a release is historical.

Changelog: added

to RunnersResolver

Changelog: added

- Add HierarchyInputType
- Add ParentLinks::CreateService
- Add HierarchyService::UpdateService

- establish baseline quereis for user ids
- remove some redundant code

Changelog: performance

GraphQL: lists the groups to where a project
can be transferred to

Changelog: added

Changelog: added

* Adds GraphQL::Ci::VariableType to be used as a generic CI variable
  type
* Adds variables field to ProjectType
* Adds variables field to GroupType
* Adds variables field to QueryType for instance variables

Changelog: added

Allows querying for a work item's assignees via GraphQL

- Add services for description widget

TASK needs to exist on the issue type enum
before enabling the `work_items` FF,but we still need to
check if the flag is enabled before allowing to create
an issue of type task