| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
Fixes the button group alignments of the threads-resolved counter and
buttons
|
|
|
|
|
| |
These dropdown buttons were missing the `btn` class, and were missing
the new button styles.
|
|
|
|
|
| |
As far as I can tell, there's no reason for the
`:not(.disabled):not(:disabled)` check here.
|
|
|
|
|
| |
This reverts commit 1cb21ec289a223fe30d2d8977f4dd0238b24c6da, reversing
changes made to 3fcf951c8bcbc5dad120e60ff4215dde2d7f3c7d.
|
|
|
|
|
| |
This reverts commit b55fc93be0d244f10960d04c7143adeb148fb4f4, reversing
changes made to f0400dc7c01ab53cdc286d639b50e1ce98a9beaf.
|
|\
| |
| |
| |
| | |
Fix QA documentation to refer to perform method
See merge request gitlab-org/gitlab-ce!30872
|
|/
|
|
|
|
| |
The documentation referred to the .act method
This MR changes this to refer to the preferred
.perform method
|
|\
| |
| |
| |
| |
| |
| | |
'10270-milestones-should-not-be-set-on-epics-issue-promotion-ce' into 'master'
CE port for milestones should not be set on epics issue promotion
See merge request gitlab-org/gitlab-ce!30633
|
|/ |
|
|\
| |
| |
| |
| |
| |
| | |
Fix bug in dashboard display of closed milestones
Closes #59381
See merge request gitlab-org/gitlab-ce!30820
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Enable RuboCop syntax linting in haml-lint
Closes #64753
See merge request gitlab-org/gitlab-ce!30903
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Also ensures we check Syntax with RuboCop, which is different.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Fix broken handling for outdated test repos
See merge request gitlab-org/gitlab-ce!30893
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The call to init had the side effect of starting another Gitaly process,
and didn't actually correctly delete the test repositories.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Update usage ping cron behavior
See merge request gitlab-org/gitlab-ce!30842
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* Splay the start by sleeping up to one minute.
* Adjust sideikiq retries to try up to approximately three hours.
* Randomize the minute fully within the hour.
* Psudo-randomize the day of the week based on the instance UUID.
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Improves add_timestamps_with_timezone helper
See merge request gitlab-org/gitlab-ce!30720
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This improves the `add_timestamps_with_timezone` helper by allowing the
column names to be configured. This has the advantage that unnecessary
columns can be avoided, saving space.
A helper for removing the columns is also provided, to be used in the
`down` method of migrations.
|
|\ \ \ \ \
| |_|_|/ /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Add Rugged calls and duration to API and Rails logs
Closes #64676
See merge request gitlab-org/gitlab-ce!30871
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This adds `rugged_duration_ms` and `rugged_calls` fields to
`api_json.log` and `production_json.log`. This will make it easier to
identify performance issues caused by excessive I/O.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/64676
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Add profile mode to extend request profiling
See merge request gitlab-org/gitlab-ce!30126
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Extend the support for "X-Profile-Token: <token>" to have an additional
header that defines type of profile we are looking for, like:
X-Profile-Mode: execution
X-Profile-Mode: memory
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Fix pid providing for Prometheus
Closes #63870
See merge request gitlab-org/gitlab-ce!30474
|
|/ / / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Use relative worker identifier for metrics (instead of Process.pid) and
identify when Unicorn/Puma/Sidekiq is used.
Previously, it was assumed that all metrics are gathered from Unicorn
due to hardcoded implementation which was incorrect.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Fix inconsistency in Redis performance bar stats
Closes #64707
See merge request gitlab-org/gitlab-ce!30866
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
peek-redis resets its counters at the start of an ActionController
notification (`start_processing.action_controller`), which causes it to
miss some Redis queries that precede it, such as the database load
balancer and Rack Attack queries. This produces inconsistencies in the
performance bar between the number of calls and their durations with the
actual calls in the detailed view.
We fix this by getting rid of peek-redis in favor of consolidating all
logic into the `RedisDetailed` view, which tracks Redis queries using
`RequestStore`. This has the nice property of removing thread-specific
counters as well.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/64707
|
|\ \ \ \ \ \ \
| |_|/ / / / /
|/| | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Resolve "Tooltips on note timestamps not showing for issues"
Closes #64669
See merge request gitlab-org/gitlab-ce!30846
|
|/ / / / / / |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
API: Allow changing only ci_default_git_depth
See merge request gitlab-org/gitlab-ce!30888
|
| | |_|/ / /
| |/| | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Refactor common Page Objects to use data tags (No. 1 Contd.)
See merge request gitlab-org/gitlab-ce!30758
|
|/ / / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Common usages within GitLab QA include Login Page,
navigation bars and layouts
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
[CE backport] Parse and store multiple security reports of the same category
See merge request gitlab-org/gitlab-ce!30658
|
|/ / / / / / |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Doc: Merge Requests for Confidential Issues
See merge request gitlab-org/gitlab-ce!30553
|
|/ / / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Add a section in Confidential Issues documentation with information
about the "Create confidential merge request" button/dropdown and how
it can help in resolving confidential issues.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Use correct parent when committing in WebIDE
See merge request gitlab-org/gitlab-ce!29598
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Previously `start_sha` was intercepted on the frontend to create the
correct branch in a separate API call. Now that the commits API supports
the `start_sha` parameter directly this workaround is not needed
anymore.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
When passing start_branch on committing from the WebIDE, it's possible
that the branch has changed since editing started, which results in the
change being applied on top of the latest commit in the branch and
overwriting the new changes.
By passing the start_sha instead we can make sure that the change is
applied on top of the commit which the user started editing from.
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Deploy serverless apps with `gitlabktl`
Closes #64494
See merge request gitlab-org/gitlab-ce!30740
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|