| Age | Commit message (Collapse) | Author |
|---|
|
Adds a clipboard button to the metrics dashboard, that allows
copying a link to an individual chart.
|
|
Add `needs:` CI config option CE
Closes gitlab-ee#12334
See merge request gitlab-org/gitlab-ce!31346
|
|
Expose finished_at for the Deployment entity
See merge request gitlab-org/gitlab-ce!31808
|
|
'47003-user-onboarding-replace-current-email-confirmation-flow-with-a-soft-email-confirmation-flow' into 'master'
Soft email confirmation flow
Closes #47003
See merge request gitlab-org/gitlab-ce!31245
|
|
- Uses vue-test-utils
- More complete coverage with parameterized tests
|
|
Enable DAG support by default
Closes #65457
See merge request gitlab-org/gitlab-ce!31814
|
|
Add key unbinds to DiscussionKeyboardNavigator
See merge request gitlab-org/gitlab-ce!31857
|
|
Resolve "Multi selection for delete on registry page"
Closes #24705
See merge request gitlab-org/gitlab-ce!30837
|
|
Add nonce to globalEval in shortcuts.js
See merge request gitlab-org/gitlab-ce!31837
|
|
Fix for role span being too 'ballooned'
Closes #65927
See merge request gitlab-org/gitlab-ce!31706
|
|
This change lays the foundation for customizable cycle analytics stages.
The main reason for the change is to extract the event definitions to
separate objects (start_event, end_event) so that it could be easily
customized later on.
|
|
Prior to 12.1, rebase status was looked up directly from Gitaly. In
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14417 , a DB
column was added to track the status instead. However, we couldn't stop
looking at the gitaly status immediately, since some rebases may been
running across the upgrade.
Now that we're in 12.3, it is safe to remove the direct-to-gitaly
lookup. This also happens to fix a 500 error that is seen when viewing
an MR for a fork where the source project has been removed.
We still look at the Gitaly status in the service, just in case Gitaly
and Sidekiq get out of sync - I assume this is possible, and it's a
relatively cheap check.
Since we atomically check and set `merge_requests.rebase_jid`, we
should never enqueue two `RebaseWorker` jobs in parallel.
|
|
- Adds UI to configure in group and project settings
- Removes notification configuration for users when
disabled at group or project level
|
|
Allow CI to clone public projects when HTTP protocol is disabled
Closes #65805
See merge request gitlab-org/gitlab-ce!31632
|
|
Also adds comment to explain why this works on the diff-tab
when it's only used in `notes-app`.
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/30144#note_204066538
|
|
Exclude json content type from workhorse interception
See merge request gitlab-org/gitlab-ce!31809
|
|
|
|
'13494-todo-s-not-rendering-when-there-is-a-design-management-related-todo-ce' into 'master'
CE backport of gitlab-org/gitlab-ee!15129 (Allow Todos to link to Designs)
See merge request gitlab-org/gitlab-ce!31789
|
|
Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/56130.
|
|
|
|
Prevents the eval script being blocked when
we have CSP rules to disable inline scripts
|
|
CE backport for gitlab-org/gitlab-ee!14097: Add merge train helper text to merge request widget
See merge request gitlab-org/gitlab-ce!30686
|
|
CE-specific changes for:
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/15129
Co-Authored-By: Alex Kalderimis <akalderimis@gitlab.com>
Co-Authored-By: Luke Duncalfe <lduncalfe@eml.cc>
|
|
This MR adds the functionality to download metrics data
as CSV. It also removes the exportMetricsToCsvEnabled feature
flag which was used before the dropdown was implemented to
display a button.
|
|
'46548-open-source-alternative-to-recaptcha-for-gitlab-com-registration' into 'master'
Open source alternative to reCAPTCHA for GitLab.com registration
See merge request gitlab-org/gitlab-ce!31625
|
|
This link is shown when a user tries to login with an unconfirmed
email address and the grace period has expired
|
|
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.
|
|
|
|
- refactor Knative and Prometheus
|
|
This introduces several changes, but these are all just ported from the
EE project.
|
|
GitLab has a mechanism that allows CI to clone repositories via HTTP
even when the HTTP protocol is disabled. This works as expected
when a project is private or internal. However, when a project is
public CI gets an error message that HTTP is not allowed. This
happens because Git only sends auth in a subsequent request after a
401 is returned first. For public projects, GitLab grabs onto that
unauthenticated request and sends it through since it recognizes
that Guests are ordinarily allowed to access the repository.
Later on this leads to a 403 since HTTP protocol is disabled.
Fix this by only continuing with unauthenticated requests when
HTTP is allowed.
|
|
|
|
'dev/security-2873-restrict-slash-commands-to-users-who-can-log-in'
|
|
into 'master'"
This reverts merge request !30808
|
|
This change adds a new counter 'cycle_analytics_views' to the usage data
metrics to count the page views for cycle analytics show page.
|
|
There were two errors: duplicate styles and @extend used with a class
name. I added `.top-area` class to all the instances where
`.wiki-page-header` is used since %top-area didn't really make a lot of
sense as a placeholder selector. This is also consistent with behaviour
on other pages where the `.top-area` class is used alongside the other
classes for the specific header styling.
|
|
Reduce Gitaly calls in PostReceive
Closes #65878
See merge request gitlab-org/gitlab-ce!31741
|
|
This toggles the ci_dag_support flag to be on by default.
This relies on ci_dag_limit_needs to be present to reduce
amount of inter-dependencies between jobs
|
|
Optimise dag processing
See merge request gitlab-org/gitlab-ce!31768
|
|
This adds a notification to let users know of our updated privacy
policy.
Users can dismiss the notification either by following the link or
closing the notification via an "x" icon.
|
|
|
|
|
|
CE backport for gitlab-org/gitlab-ee!14894: Fix the merge button dropdown
See merge request gitlab-org/gitlab-ce!31248
|
|
|
|
Adjust copy for adding additional members
See merge request gitlab-org/gitlab-ce!31726
|
|
Fix project avatar image in Slack pipeline notifications
Closes #66008
See merge request gitlab-org/gitlab-ce!31788
|
|
Source Code Usage Ping for Create SMAU
|
|
Expand variables only when needed
See merge request gitlab-org/gitlab-ce!31772
|
|
**Prevention of running 2 simultaneous updates**
Instead of using `RemoteMirror#update_status` and raise an error if
it's already running to prevent the same mirror being updated at the
same time we now use `Gitlab::ExclusiveLease` for that.
When we fail to obtain a lease in 3 tries, 30 seconds apart, we bail
and reschedule. We'll reschedule faster for the protected branches.
If the mirror already ran since it was scheduled, the job will be
skipped.
**Error handling: Remote side**
When an update fails because of a `Gitlab::Git::CommandError`, we
won't track this error in sentry, this could be on the remote side:
for example when branches have diverged.
In this case, we'll try 3 times scheduled 1 or 5 minutes apart.
In between, the mirror is marked as "to_retry", the error would be
visible to the user when they visit the settings page.
After 3 tries we'll mark the mirror as failed and notify the user.
We won't track this error in sentry, as it's not likely we can help
it.
The next event that would trigger a new refresh.
**Error handling: our side**
If an unexpected error occurs, we mark the mirror as failed, but we'd
still retry the job based on the regular sidekiq retries with
backoff. Same as we used to
The error would be reported in sentry, since its likely we need to do
something about it.
|
|
Only expire tag cache once per push
See merge request gitlab-org/gitlab-ce!31641
|
