Denys Mishunov authored 5 years ago and Filipa Lacerda committed 5 years ago

Resolves a regression caused by https://bit.ly/2k1GozA

Creating a MR from an issue using a tag as ref correctly creates the
source branch starting from the tag.

Creates vue and vuex support for new job log

Creates the new log.vue component to handle the
new format
Updates the store to use the new parser
Creates an utility function to handle the
incremental log

- Show if user can_resolve all of the notes

This reverts commit f222e74d455ec9fc10efb783ffe4684836cc1c3b.

* Switched from Karma to Jest
* Reorganized tests to have correct semantics
* Removed unused computed properties from component

https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/32554 removed the
support_bot column, but nodes were not told to ignore this column.
As a result, after the post-deploy migration ran, nodes attempted
to use this column, causing 500 errors.

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

- Load EKS create cluster form as dynamic import dependency.
- Include aws-sdk dependency in package.json

- Add AWS SDK Dependency
- Create placeholders for Vue components
- Create store with state structure

Refactor project_edit.js to be reusable for this purpose

Closes #64799

This change updates the text of the pipeline widget that appears on the
merge request page. The text has been made more consistent between
different types of pipelines; this makes the front-end implementation
simpler and more maintainable.  In addition, the type of pipeline is
(i.e. regular pipeline, merge request pipeline, detached pipeline)
included in the text, making this type more obvious to the end user.

Some information has been removed from the widget as part of this
change; however, any information that was removed already appears
elsewhere on the merge request page.

In the Merge Request view, under pipelines tab
the user can see a run pipeline button

Adds axios post request to button click

Adds the logic to handle the user click,
refresh the table and disable the button while thee
request is being made

Updates UI for desktop and mobile

Adds specs
Regenerates potfile

Follow-up after review

Uses .finally to avoid code repetition

Alessio Caiazza authored 5 years ago and Mayra Cabrera committed 5 years ago

Backporting https://github.com/rmosolgo/graphiql-rails/pull/71

Fernando Arias authored 5 years ago and Paul Slaughter committed 5 years ago

**Why?**
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/15015#note_210891978

Winnie Hellmann authored 5 years ago and Paul Slaughter committed 5 years ago

Fixes https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/32400

Add qa selectors to wiki show and ssh keys page
Add method to wiki push resource to find ssh_uri

Dmitriy Zaporozhets authored 5 years ago and Peter Leitzen committed 5 years ago

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Imports the files needed for the custom
stage form and adds the EE specific css.

Added stub addStageMixin

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

For zero-downtime deployed in a mixed code environment between 12.2 and
12.3, the branch and tag name cache is incorrectly invalidated - a push
to an old machine will not clear the redis set version of the cache on
the new machine.

This commit ensures that, in 12.3, both set and non-set versions of the
cache are invalidated, but does not write or consult the set version of
the cache. . In 12.4, it will be safe to switch branch and tag names to
the redis set cache both it and the legacy cache will be invalidated
appropriately in such a mixed code environment.

This delays the full implementation of the feature by one release, but
in the absence of a credible feature-flagging strategy, and amidst an
abundance of caution about the effects of too-eager cache expiration, I
believe this is the best approach available to us.

We had similar code in a few places to redirect to the last page if
the given page number is out of range. This unifies the handling in a
new controller concern and adds usage of it in all snippet listings.

- Avoid N+1 queries for authors and comment counts
- Avoid an additional snippet existence query

This reverts commit c6ccc07f.

It consists of two parts:

1. Redirecting users to the configured external storage
1. Allowing the external storage to request the static object(s)
   on behalf of the user by means of specific tokens

Part of https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/6829

In case the source and the target project are the same, the
source branch is the default branch, and the target branch
is not present, we will avoid prefilling the target branch
with the repository default branch. Letting the user decide.

This presenter will be used in an upcoming MR which adds
rendering of epic events on group activity page.