| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
This commit does a find-and-replace from ATMTWPS -> MTWPS.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
This commit adds a helper text that describes what will happen when a
user clicks the "Start/Add to merge train when pipeline succeeds"
button. This text appears at the bottom of the merge request widget.
In addition, this commit renames the "merge_train_info" component to
"merge_train_position_indicator" to avoid ambiguity with the
"merge_train_helper_text" component.
|
| |
|
|
|
|
|
|
|
| |
Splits auto-refreshing of MR widget into 2 requests:
- the one which uses etag-caching and invalidates the fields on change
- the one without caching
The idea is to gradually move all the fields to etag-cached endpoint
|
| |
|
|
|
|
| |
This commits extracts /merge_requests/1.json?serializer=widget
Into a separate /merge_requests/1/widget.json endpoint
This will allow to use caching for this request
|
| |
|
|
|
| |
This commit updates the merge request widget's "Merge" button to
support merge trains.
|
| |
|
|
|
|
|
|
| |
This commit is the result of running `yarn eslint --fix` after enabling
the `no-implicit-coercion` ESLint rule. This rule has been added to
our ESLint config here:
https://gitlab.com/gitlab-org/gitlab-eslint-config/merge_requests/14
|
| |
|
|
|
| |
A few minor frontend changes to complete the refactoring
from MWPS to the more generic autoMergeStrategy.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
We have one auto merge strategy today - Merge When Pipeline
Succeeds.
In order to add more strategies for Merge Train feature,
we abstract the architecture to be more extensible.
Removed arguments
Fix spec
|
| |\
| |
| |
| |
| |
| |
| | |
into 'master'
Update merge request widget to accommodate post-merge pipelines
See merge request gitlab-org/gitlab-ce!25983
|
| | |
| |
| |
| |
| | |
This commit adds two new warning messages to the MR widget that handle
cases involving merge request pipelines.
|
| |/ |
|
| | |
|
| | |
|
| |
|
|
| |
(cherry picked from commit 5c35cdc929abf5251512ba6ddf7078e570232709)
|
| |
|
|
| |
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/53463
|
| |
|
|
|
|
| |
Update changelog to include Merge Request ID and Author
Update changelog to include Merge Request ID and Author
|
| | |
|
| |\
| |
| |
| |
| |
| |
| |
| |
| | |
'41545-gitlab-merge-request-status-could-not-connect-to-the-ci-server-please-check-your-settings-and-try-again' into 'master'
Resolve "Reword error message for internal CI unknown pipeline status"
Closes #53056
See merge request gitlab-org/gitlab-ce!22474
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
| |
|
|
|
|
|
| |
Creates an app to render grouped test reports in the MR widget
Ports CSS from EE into CE
Creates a reusable code component
Adds getters and utils to the existing reports store
|
| |
|
|
| |
Closes #47460
|
| |
|
|
| |
button
|
| |
|
|
|
|
| |
branch"
"Maintainer" will be freed to be used for #42751
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
When a project is not private, and the source branch not protected the
user can now select the option to allow maintainers to push to this
branch
|
| |
|
|
| |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
When a project uses fast-forward merging strategy user has
to rebase MRs to target branch before it can be merged.
Now user can do rebase in UI by clicking 'Rebase' button
instead of doing rebase locally.
This feature was already present in EE, this is only backport
of the feature to CE. Couple of changes:
* removed rebase license check
* renamed migration (changed timestamp)
Closes #40301
|
| |
|
|
| |
closed/merged
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Fix https://gitlab.com/gitlab-org/gitlab-ce/issues/38389
|
| |\
| |
| |
| |
| |
| |
| | |
Fixes merge request widget date tooltip inconsistencies
Closes #38545
See merge request gitlab-org/gitlab-ce!14578
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously the merge request widget would use the `updated_at` date as
the tooltip text for both closed & merged states. This is incorrect as
the `updated_at` date is actually changed when a user updates merge
request through commenting, description changes or anything else.
The widget states for merged & closed events now use their own event
object which holds their own `updated_at` date string. Also this text
has been correctly formatted through our date utilities to correctly
display the right timezone data in a user friendly way.
Closes #38545
|
| | | |
|
| |/
|
|
| |
See https://gitlab.com/gitlab-org/gitlab-ce/issues/20076
|
| |
|
|
|
|
|
|
| |
Fix https://gitlab.com/gitlab-org/gitlab-ce/issues/33287
The MR widget was trying to render the pipelines section when
there are no GitLab CI pipelines which was throwing some NPE
errors.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Having two states that essentially mean the same thing is very much like
having a boolean "true" and boolean "mostly-true": it's rather silly.
This commit merges the "reopened" state into the "opened" state while
taking care of system notes still showing messages along the lines of
"Alice reopened this issue".
A big benefit from having only two states (opened and closed) is that
indexing and querying becomes simpler and more performant. For example,
to get all the opened queries we no longer have to query both states:
SELECT *
FROM issues
WHERE project_id = 2
AND state IN ('opened', 'reopened');
Instead we can query a single state directly, which can be much faster:
SELECT *
FROM issues
WHERE project_id = 2
AND state = 'opened';
Further, only having two states makes indexing easier as we will only
ever filter (and thus scan an index) using a single value. Partial
indexes could help but aren't supported on MySQL, complicating the
development process and not being helpful for MySQL.
|
| | |
|
| | |
|
