gitlab.com admins can view/update runners minutes cost factor,
these fields appear now in the Vue UI.

- Public projects Minutes cost factor
- Private projects Minutes cost factor

When a due date falls on the current date,
it should not be considered expired.

expiredLast is more appropriate
as a sort option since it is a specialized
case of due date sorting.

- Annotate using :aggregate_failures over wrapping in blocks
- DRY creating objects and specs

These changes are made to milestone-related GraphQL APIs.

- Milestone type gets a new 'expired' field indicating
whether milestone's due date is past the current date.

- When listing milstones, these arguments can be specified:

  - 'expiredLast' sorts milestones in layers:
  Current miletones are placed first, followed by
  milestones without due dates and expired milestones.
  Within layers, milestones are sorted by due date
  (asc by default) with ties being broken by id (desc).
  When 'expiredLast' is set, 'sort' argument other than
  due_date_desc or due_date_asc is ignored.

  - 'sort'

Changelog: added

A new method is added to the milestone model
to support fetching milestones in this particular order:
1. Current milestones (due date > current date)
2. Milestones without due dates
3. Milestones that are expired (due date <= current_date)

The milestones are then sorted by due date (asc or desc)
and ties are broken by id in descending order.

The milestone finder is also updated to accept
a new Boolean parameter 'expired_last' to utilize the
newly added custom ordering to fetch milestones.

When 'expired_last' is specified, order param must be
one of 'due_date_asc' or 'due_date_desc'. For non-supported
order param values (including when it's not provided),
the default is 'due_date_asc'.

Refactor to use let_it_be and build wherever suitable
to improve test performance.

Changelog: performance

This will ensure the namespaces are
displayed in alphabetical order by its name.

Changelog: changed

Prior to version 12, Postgres did not support foreign keys where the
target table was a partitioned table. The database team had begun work
on a custom solution to solve this problem, but as we're not on v12,
it's no longer needed. Removing all the related code.

This change update error reporting to Sentry in the runner UI and
adds more specific flash messages to the user.

Build out the new token access
section in Vue and GraphQl. Also
add docs and test coverage.

- Introduce service object to remove project from scope
- Use new service object in new GraphQL mutation

Changelog: added

When instance_url is set the JiraConnectInstallation
serves as proxy for a self-managed instance. In this
case it should forward the event.

Remove feature flag `projects_post_creation_worker`

Changelog: other

Add user timezone when transmitting user information through gRPC.
Need to upgrade gitaly Gem to "14.1.0.pre.rc2".
Add feature flag: add_timezone_to_web_operations.
See: gitaly!3586

Changelog: added

Changelog: added

With the old logic, having a single stale/lagging replica would not
allow us to use caught up replicas, which would increase the load to
primary where we could avoid it. Also adding the comments on the
possible improvements of the similar method.

Changelog: performance

Kerri Miller authored 3 years ago and Nikola Milojevic committed 3 years ago

Especially for APIs, we need to ensure that we're returning an actual
true/false value and not a nil or other value that would be falsy

When the user who merged the Github Pull Request was deleted, github API
sends `nil` in the `merged_by` field. To avoid an exception, when
creating the complementary note that mentions the original merger user,
fallbacks to 'ghost' in the note.

Related to: #334213
MR: !65152
Changelog: fixed

Changelog: added