| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| |
| |
| | |
Upgrade Gitaly to v1.26.0
See merge request gitlab-org/gitlab-ce!25890
|
|/ |
|
|\
| |
| |
| |
| |
| |
| | |
'58304-extend-the-snowplow-event-tracking-documentation-with-a-testing-section' into 'master'
Resolve "Extend the "Snowplow event tracking" documentation with a "testing" section"
See merge request gitlab-org/gitlab-ce!25612
|
|/
|
|
| |
section"
|
|\
| |
| |
| |
| | |
Created documentation for replying to comments
See merge request gitlab-org/gitlab-ce!25633
|
| |\
| | |
| | |
| | | |
# Conflicts:
# doc/user/discussions/index.md
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
replies
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Added documentation for starting a discussion from a
non-discussion comment feature.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Unquarantine fixed tests
See merge request gitlab-org/gitlab-ce!25875
|
| | |/
| |/|
| | |
| | | |
Fix: https://gitlab.com/gitlab-org/gitlab-shell/merge_requests/280
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Fix "yarn-deduplicate has unmet dependencies"
See merge request gitlab-org/gitlab-ce!25885
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Fix for mismatch in EE on FIXTURE_PATHS to FIXTURE_PATH
Closes gitlab-ee#10266
See merge request gitlab-org/gitlab-ce!25878
|
| | |/ /
| |/| |
| | | |
| | | | |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Display Ancestors in Issuable Sidebar
See merge request gitlab-org/gitlab-ce!25886
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Resolve "Improve stop pipeline modal"
Closes #46464
See merge request gitlab-org/gitlab-ce!25059
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Make it its own component
Show pipeline status and link to pipeline
Show commit short hash, link, and message
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Resolve "Project template for iOS"
Closes #58648
See merge request gitlab-org/gitlab-ce!25872
|
|/ / / / / |
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Resolve "Hashed storage migration should not be attempted if project does not validate"
Closes #56618
See merge request gitlab-org/gitlab-ce!25753
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This is a fix for the Hashed Storage migration and Rollback procedure
to ignore any project-level validation error that can happen in a
long-running instance.
There are many situations where defaults and acceptable values changed
but, because we didn't provide a migration to "valid" attributes, it
can happen that project will not be `valid? => true`.
Because the changes we are making are limited to setting a project as
read_only or changing the storage_level, it's safe to bypass validation.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Use date for upcoming milestone comparison
Closes #58325
See merge request gitlab-org/gitlab-ce!25806
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
`NOW()` is a timestamp, with a maximum year (in Postgres) 294276 AD.
`milestones.due_date` is a date with a maximum year (again, in Postgres)
of 5874897 AD.
If there is a due date past the limit for the timestamp, comparing the
two will fail with:
ERROR: date out of range for timestamp
We also need to add validations to keep the due dates sensible, but for
now we can simply use `CURRENT_DATE` instead of `NOW()`, so the types
match with no coercion needed.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
When looking for upcoming milestones, we compare the milestone's due
date to `NOW()`. However, the due date is a date and `NOW()` is a
timestamp, and in Postgres, timestamps can't extend as far in the future
as dates can.
This test exposes the issue.
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Incremental backups
See merge request gitlab-org/gitlab-ce!24035
|
| | | | | | | | |
|
| | | | | | | | |
|
| |\ \ \ \ \ \ \ |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
|\ \ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
Adding additional usage metrics for Release to weekly ping
See merge request gitlab-org/gitlab-ce!25014
|
|/ / / / / / / / / |
|
|\ \ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
Resolve "Mask the existing variables"
Closes #58010
See merge request gitlab-org/gitlab-ce!25868
|
|/ / / / / / / / / |
|
|\ \ \ \ \ \ \ \ \
| |_|_|_|_|_|/ / /
|/| | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Remove translation dependency in CA spec
Closes #58653
See merge request gitlab-org/gitlab-ce!25882
|