| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
| |
Navigating to the "Members" section of a project would omit the
relative URL root path. Fix the redirection and eliminate the
need for a redirection in the first place.
Fix other redirections failing to work with relative roots
|
|
|
|
|
|
| |
configuration page
Closes #25142
|
|\
| |
| |
| |
| |
| |
| | |
Backport EE changes to group routes
Closes gitlab-ee#3794
See merge request gitlab-org/gitlab-ce!14973
|
| | |
|
|\ \
| |/
|/|
| |
| |
| |
| | |
Show Gitaly data in the peek performance bar
Closes #39231
See merge request gitlab-org/gitlab-ce!14949
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Because container registry tags can have periods, the addition of the `.json`
format caused ambiguity. Since the tag name regex is greedy, it would attempt
to locate an image named `foo.json` instead of `foo`.
Closes #39260
|
|/ |
|
|
|
|
| |
host is omitted by default
|
| |
|
|\
| |
| |
| |
| | |
Make the circuitbreaker configurable at runtime
See merge request gitlab-org/gitlab-ce!14842
|
| |
| |
| |
| | |
Instead of from the configuration file
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Show collapsible tree on the project show page
Closes #30343
See merge request gitlab-org/gitlab-ce!14055
|
| | | |
|
| |\ \ |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Remove "boards" from TOP_LEVEL_ROUTES
Closes #39073
See merge request gitlab-org/gitlab-ce!14861
|
| | |_|/
| |/| | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
'master'
Resolve "GitlabUsagePingWorker is not running on GitLab.com"
See merge request gitlab-org/gitlab-ce!14867
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
On GitLab.com, we see that cron jobs sometimes don't run. This appears to be
because the process that polls for current cron jobs only has a 60 second
validity period, so if (for whatever reason) it misses those 60 seconds, we have
to wait until the next execution.
For the usage ping, this is particularly problematic, as that's only scheduled
to run once a week.
Changing it to run for every minute in a 10 minute period should work around
this, if the above diagnosis is correct. The job itself obtains an exclusive
lease for 24 hours, so rescheduling in quick succession is safe.
|
|\ \ \ \
| |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | | |
Upgrading Monaco
Closes #38607
See merge request gitlab-org/gitlab-ce!14629
|
| |/ / |
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Add support for markdown preview to group milestones
Closes #30241
See merge request gitlab-org/gitlab-ce!14806
|
| | |/
| |/| |
|
|/ / |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Create idea of read-only database
Closes #37534
See merge request gitlab-org/gitlab-ce!14688
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In GitLab EE, a GitLab instance can be read-only (e.g. when it's a Geo
secondary node). But in GitLab CE it also might be useful to have the
"read-only" idea around. So port it back to GitLab CE.
Also having the principle of read-only in GitLab CE would hopefully
lead to less errors introduced, doing write operations when there
aren't allowed for read-only calls.
Closes gitlab-org/gitlab-ce#37534.
|
|/ / |
|
|\ \
| | |
| | |
| | | |
feature/sm/35954-create-kubernetes-cluster-on-gke-from-k8s-service
|
| |\ \
| | | |
| | | |
| | | |
| | | | |
Send API parameters as extra data for sentry errors
See merge request gitlab-org/gitlab-ce!14644
|
| | | | |
|
| |\ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Upgrade doorkeeper-openid_connect
See merge request gitlab-org/gitlab-ce!14372
|
| | | | | |
|
|\ \ \ \ \
| |/ / / /
| | | | |
| | | | | |
feature/sm/35954-create-kubernetes-cluster-on-gke-from-k8s-service
|
| |\ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Add external link for online artifacts
Closes #34102
See merge request gitlab-org/gitlab-ce!14399
|
| | | | | | |
|
| | |\ \ \ \ |
|
| | | | | | | |
|
| | | |_|/ /
| | |/| | | |
|
| | | | | | |
|
|\ \ \ \ \ \
| |/ / / / /
| | | | | |
| | | | | | |
feature/sm/35954-create-kubernetes-cluster-on-gke-from-k8s-service
|
| |\ \ \ \ \
| | | |_|_|/
| | |/| | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
digitalmoksha/gitlab-ce-feature/verify_secondary_emails
# Conflicts:
# app/controllers/admin/users_controller.rb
# app/controllers/confirmations_controller.rb
# app/controllers/profiles/emails_controller.rb
# app/models/user.rb
# app/services/emails/base_service.rb
# app/services/emails/destroy_service.rb
# app/views/devise/mailer/confirmation_instructions.html.haml
# lib/api/users.rb
# spec/services/emails/destroy_service_spec.rb
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
and rubocop fixes
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
for `emails` to be a top level route
|