Just replace RSA.new with PKey.read

Detect if pipeline runs for a GitHub pull request

When using a mirror for CI/CD only we register a pull_request
webhook. When a pull_request webhook is received, if the
source branch SHA matches the actual head of the branch in the
repository we create immediately a new pipeline for the
external pull request. Otherwise we store the
pull request info for when the push webhook is received.

When using "only/except: external_pull_requests" we can detect
if the pipeline has a open pull request on GitHub and create or
not the job based on that.

Etienne Baqué authored 5 years ago and Andreas Brandl committed 5 years ago

Modified schema via migrations.
Added one-to-one relationship between the two models.
Added changelog file

Manoj M J authored 5 years ago and Mayra Cabrera committed 5 years ago

This change limits the number of emails
for new access requests notifications to
10 most recently active owners/maintainers

Heinrich Lee Yu authored 5 years ago and Patrick Derichs committed 5 years ago

Also change test URL sequest to .test TLD

Also change test URL sequest to .test TLD

- move uploads created by AttachmentUploader
- handle also files created for legacy_diff_notes

- Adds UI to configure in group and project settings
- Removes notification configuration for users when
disabled at group or project level

Creating new records has been disabled, and all
existing records been migrated to clusters as of
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/28534

Tiger Watson authored 5 years ago and Thong Kuah committed 5 years ago

Kubernetes deployments on new clusters will now have
a separate namespace per project environment, instead
of sharing a single namespace for the project.

Behaviour of existing clusters is unchanged.

All new functionality is controlled by the
:kubernetes_namespace_per_environment feature flag,
which is safe to enable/disable at any time.

We had a number of team members struggle to find invited members of a
group. Searching for the e-mail address did not work because search only
works with members with user accounts.

This commit changes two things:

1. Breaks out the invited members into a separate table.
2. Adds search capability for the invited members.

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/61948

Ports changes from
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/12343

Introducing Docker Registry replication

This implements the support for `needs:` keyword
as part of GitLab CI. That makes some of the jobs
to be run out of order.

- the typo in this factory name was precluding us from properly
creating dynamic code to remove duplciation.

Adds Job specific variables to facilitate specifying variables when
running manual jobs.

Using the sed script from
https://gitlab.com/gitlab-org/gitlab-ce/issues/59758

Luke Duncalfe authored 5 years ago and James Lopez committed 5 years ago

A project can have the same `LfsObject` linked with up to three
`LfsObjectsProject` records. Each of these records would be for a
different repository, recorded in the `repository_type` property. The
different repositories at time of writing are "project", "wiki", and
"design". See https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/13894

This change exports the list of `repository_type`s as a JSON mapping of
oid => repository_types, which are imported to recreate the correct
`LfsObjectsProject` records.

https://gitlab.com/gitlab-org/gitlab-ee/issues/11090

vshushlin authored 5 years ago and Nick Thomas committed 5 years ago

This validation prevents the domain from being saved from the UI
e.g. when user tries to enable Let's Encrypt integration

- Migration updates existing groups to "owner", then sets default to
  "maintainer" so that new groups will default to that
- Update spec examples

This setting is at the group level only. The default is specified to
be maintainers and owners.

**Specs only**, all failing.

- Migration updates existing groups to "owner", then sets default to
  "maintainer" so that new groups will default to that
- Update spec examples

This setting is at the group level only. The default is specified to
be maintainers and owners.

**Specs only**, all failing.

- Migration updates existing groups to "owner", then sets default to
  "maintainer" so that new groups will default to that
- Update spec examples

This setting is at the group level only. The default is specified to
be maintainers and owners.

**Specs only**, all failing.

- Migration updates existing groups to "owner", then sets default to
  "maintainer" so that new groups will default to that
- Update spec examples

This setting is at the group level only. The default is specified to
be maintainers and owners.

**Specs only**, all failing.