Enable the propagation of all of the job ENV
vars to the sast docker container and thus to
the analyzer containers being started by it.
This enables passing credentials for private
repos being accessed by underlying analyzers
via UI-set environment variables. Exclude a
bunch of system-related ENV vars from
propagation.

Truncate recommended branch name to a sane length

See merge request gitlab-org/gitlab!18821

Add elastic-stack as gitlab managed app

See merge request gitlab-org/gitlab!18015

Add a new gitlab-managed app for the elastic stack

[ci skip]

[ci skip]

Merge branch '32961-hosted-website-on-gitlab-pages-asking-for-authorization-via-oauth-login' into 'master'

Resolve "Hosted website on Gitlab Pages asking for authorization via OAuth login."

Closes #32961

See merge request gitlab-org/gitlab!18386

We've enabled access control for pages on .com 2.5 months
after the migration fixing settings were run.

All private projects created withing this timeframe have
access control enabled but users do not know that.

We add rake task which will find such projects and reset
settings to the anticipated state.

Add split button to create issue from epics tree

See merge request gitlab-org/gitlab!17948

Enable epic events on group activity page

Closes #7385

See merge request gitlab-org/gitlab!18869

More fine-grained metrics for sidekiq workers

Closes #32258

See merge request gitlab-org/gitlab!18817

We currently only measure the global (node-level) business in terms
of jobs being processed. We would instead like to be able to know
for each sidekiq process how saturated it is in terms of actual
concurrency vs requested/max concurrency.

This patch does the following:

- add a worker/process dimension to all existing metrics
- introduce a new metric to observe concurrency per process

by relating "actual job count per process" to "max job count per
process" we can then obtain some sort of saturation metric.

Block MR with OMIPS on skipped pipelines

Closes #30059

See merge request gitlab-org/gitlab!18838

Add storage shards wording

See merge request gitlab-org/gitlab!18732

API call for Resolve Vulnerability

See merge request gitlab-org/gitlab!18439

Add resolve_vulnerability ability for User.
Add POST /vulnerabilities/:id/dismiss API.
Add computed state to Findings. Update
the related finder and associations to
support that computed state.

Change url for tag push events in chat message integration

See merge request gitlab-org/gitlab!18126

Instead of the branch_url being set to `/commits/<ref>` for both tags
and regular pushes, branch_url is conditionally set to `/-/tags/<ref>`
for tags.

add dummy project data for push sample data

See merge request gitlab-org/gitlab!18571

Improve pod logs API

See merge request gitlab-org/gitlab!17881

- The rollout_status is required to get pod_names, so return nil, which
will cause the controller to return 202 or 204.
- Return additional parameters like pods, pod_name, container_name.
- pods is the names of all pods of this environment.
- Return error when no pods are available.
- pod_name is the name of the pod whose logs are being returned.
- container_name is the name of the container within the pod whose logs
are being returned. container_name can be nil when the request to k8s
API was made without a container_name.

Rename user_id to author_id for Versions

See merge request gitlab-org/gitlab!18506

Add comment clarifying cache behavior of `GrafanaMetricsEmbedService`

Closes #34526

See merge request gitlab-org/gitlab!18881

Signed-off-by: Balasankar "Balu" C <balasankar@gitlab.com>

Fix flaky 25_downstream_pipelines fixture

See merge request gitlab-org/gitlab!18922

Make documentation linter show target path

See merge request gitlab-org/gitlab!18895

- We are seeing flaky documentation lint checks that do not always catch
  when a file inside the documentation is set with the executable bit.
  The check to find executable documents runs inside a subshell and its
  error output is not being redirected, nor would it count those errors
  when running `wc -l`. It seems implausible that we are failing to `cd`
  into the correct directory, but this is the one method I know of that
  would cause the `find` expression to fail silently in the logs. It is
  also just useful to see that yes, we are running the documentation
  linter against a reasonable directory in the logs.

Related https://gitlab.com/gitlab-org/gitlab/issues/28010Signed-off-by: Robert Marshall <rmarshall@gitlab.com>

Signed-off-by: Balasankar "Balu" C <balasankar@gitlab.com>

Re-raise exception if there is no response

Closes #34332

See merge request gitlab-org/gitlab!18856

It's possible that `rescue ExceptionWithResponse` could catch a
type of exception that has no response. So we need to check if there
is a response before we return it

Allow Gitaly to work without a PG connection

Closes #34205

See merge request gitlab-org/gitlab!18659

Gitaly didn't require a PG connection to connect to, though recently we
started to pass feature flags to Gitaly in different manners. That
change would now require a PG to be running. This is not ideal,
especially if only for feature flags.

This change rescues a bad connection error, and breaks the required
dependency between PG and Gitaly.

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

Add more information for pre and post

See merge request gitlab-org/gitlab!18773