Also refactor some of the code in multiversion component.

When we use the multiversion select to choose which
version of GitLab we want to use (.com or self-hosted),
we need to reload the page in order to update the
Content Security Policy from the backend to include
the new URL of the self-hosted instance.

Thus we need to store the baseURL to localStorage on
initial save, reload the page then retrieve it.

When user is signed in, we send the `sign-in-oauth` event
from the SignInPage. However, the rendering of this
component depends on the `userSignedIn` condition
which causes the event to not bubble properly.

Updated documentation with environment (batch 6)

See merge request !96830

Destroy invalid project members

See merge request !95881

Refactor API calls to support calls to a self-hosted instance for Jira connect app

See merge request !96677

Justin Ho Tuan Duong authored 2 years ago and Simon Knox committed 2 years ago

In the scenario where Jira connect is setup for self-hosted,
most API calls will be made to this self-hosted instance
instead of GitLab.com. Thus we need a different axios
instance which will have a baseURL that points to the
self-hosted GitLab instance.

Updated documentation with environment (batch 1)

See merge request !96816

Streamlines redirect steps

See merge request !96819

Suzanne Selhorn authored 2 years ago and Russell Dickenson committed 2 years ago

Attempting to make them easier to scan

Added check for Advanced Search migrations

See merge request !96719

Add a note about SCIM providers

See merge request !96911

Update CODEOWNERS to support segregation of duties

See merge request !96696

Update CODEOWNERS with new paths

See merge request !96697

Phillip Wells authored 2 years ago and Kati Paizee committed 2 years ago

Some areas could be condensed to save space
and improve legibility. An attempt to strike a 
balance between ease of updating, and length 
of declaration.

Update script to (optionally) revoke actively used PATs

See merge request !96404

Jessie Young authored 2 years ago and Mayra Cabrera committed 2 years ago

* In the first iteration of this class, the "cut off date" was used to
  revoke personal access tokens that were last used before that date.
* In that context, this was a class for revoking unused PATs.
* This MR makes it possible to run this class so that the "cut off date"
  is to revoke any tokens created before that date, irrespective of
  when they were last used. So it now works for both used and unused
  PATs.
* First MR: !95340

Add (days) as unit to VSA duration chart

See merge request !96358

Adam Hegyi authored 2 years ago and Paul Slaughter committed 2 years ago

- !96358

Changelog: changed
EE: true

Do not show revoke button if revoke_path is absent

See merge request !96276

Eduardo Sanz García authored 2 years ago and Paul Slaughter committed 2 years ago

`AccessTokenTableApp` component assumed that `revoke_path` in the access
token is always present. However, the property `revoke_path` is
optional.

When the `revoke_path` is absent or **falsy** it doesn't display the
revoke button action.

Changelog: changed

Move general console tips

See merge request !96928

Merge branch '358148-remove-ci-related-metrics-from-usage_activity_by_stage_secure-from-usage_data-rb' into 'master'

Remove secure product metrics from usage_data.rb

See merge request !96510

Niko Belokolodov authored 2 years ago and Kerri Miller committed 2 years ago

This removes metrics generation from usage_data.
Instrumentation classes were added in 339447

Add why default branch scans are important

See merge request !96831

Prefer first(1) instead of [0...1] in Sentry specs

See merge request !96861

Add filtering by type to EnvironmentsFinder

See merge request !96668

Finalize removal of incorrect issue indexes

See merge request !96743

Update code review approval guidelines

See merge request !96689

Make sure we run rspec-all frontend_fixture as-if-foss for jest as-if-foss

See merge request !96910

Move rails sign in method

See merge request !96920