| Age | Commit message (Collapse) | Author |
|---|
|
These upgrades are necessary to support Ruby 2.6.
This matches the Gitaly MR:
https://gitlab.com/gitlab-org/gitaly/merge_requests/1066
|
|
This reverts commit e8c1c930c3bc7c159463ed3bed8765db01b40328.
|
|
Update GitLab Runner Helm Chart to 0.4.0/11.10.0
See merge request gitlab-org/gitlab-ce!27508
|
|
|
|
Show prioritized labels to guests
Closes #57247
See merge request gitlab-org/gitlab-ce!27307
|
|
|
|
[ci skip]
|
|
|
|
Add configuration of access_level for runners on registration via API
See merge request gitlab-org/gitlab-ce!27490
|
|
Disables sorting when guests are viewing
|
|
Bump required Ruby version check to 2.5.3
Closes #60704
See merge request gitlab-org/gitlab-ce!27495
|
|
Relates to https://gitlab.com/gitlab-org/gitlab-ce/issues/58079
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/60704
|
|
|
|
'master'
CE Backport for "Restructure project merge request settings page"
See merge request gitlab-org/gitlab-ce!26834
|
|
* On the project labels page, the label itself should not be clickable.
* On the group labels page, the links for Issues and Merge Requests should be shown.
|
|
|
|
Allow setting access_level of new runner to not_protected (default) or ref_protected
Minor update to relevant docs and tests
|
|
Migrate correlation and tracing code to LabKit
See merge request gitlab-org/gitlab-ce!25379
|
|
|
|
Only use backslash escapes in autocomplete when needed
Closes #45348
See merge request gitlab-org/gitlab-ce!27457
|
|
Extract discussion actions into separate component
Closes #58293
See merge request gitlab-org/gitlab-ce!27227
|
|
This change is a fairly straightforward refactor to extract the tracing
and correlation-id code from the gitlab rails codebase into the new
LabKit-Ruby project.
The corresponding import into LabKit-Ruby was in
https://gitlab.com/gitlab-org/labkit-ruby/merge_requests/1
The code itself remains very similar for now.
Extracting it allows us to reuse it in other projects, such as
Gitaly-Ruby. This will give us the advantages of correlation-ids and
distributed tracing in that project too.
|
|
|
|
'60500-disable-jit-kubernetes-resource-creation-for-project-level-clusters' into 'master'
Disable JIT Kubernetes resource creation for project level clusters
Closes #60500
See merge request gitlab-org/gitlab-ce!27352
|
|
|
|
- Created DiscussionActions component
- Updated NoteableDiscussion component accordingly
- Wrote Jest tests for DiscussionActions
- Updated Jest config to enable emojis aliases mock
- Updated qa specs to reflect changes in NoteableDiscussions
|
|
This commit updates the CE-specific files that reorganizes the project
merge request settings UI.
|
|
Only show author in autocomplete dropdown if author is active
See merge request gitlab-org/gitlab-ce!27292
|
|
#57815 Omniauth UltraAuth strategy
See merge request gitlab-org/gitlab-ce!26348
|
|
Bring back Rugged implementation of ListCommitsByOid
See merge request gitlab-org/gitlab-ce!27441
|
|
Add backtrace to Gitaly performance bar
Closes #60092
See merge request gitlab-org/gitlab-ce!27345
|
|
Autocompletion for references happens on the frontend. Those references
are turned into actual references on the backend, but only after
Markdown processing has happened. That means that if a reference
contains a character that Markdown might consume, it won't render
correctly. So we need to do some escaping on the frontend.
We have these potential problem characters:
https://docs.gitlab.com/ee/user/markdown.html#emphasis
1. ~ - this is ~~strikethrough~~, but only when doubled.
2. _ - used for _emphasis_, doubled is __bold__.
3. * - also used for *emphasis*, doubled is **bold** also.
4. ` - used for `code spans`, any number works.
We don't need to escape `-` any more. When it comes to being inside a
word:
1. a~~b~~ has strikethrough, so it needs to be escaped everywhere.
2. a_b_ has no emphasis (see [a]) so it only needs to be escaped at the
start and end of words.
3. a*b* has emphasis, so it needs to be escaped everywhere.
4. a`b` has a code span, so it needs to be escaped everywhere.
Or, in code terms:
1. Always escape ~~, *, and ` when being inserted by autocomplete.
2. Escape _ when it's either at the beginning or the end of a word.
[a]: https://docs.gitlab.com/ee/user/markdown.html#multiple-underscores-in-words
|
|
This brings back changes in
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/20432.
For users using Gitaly on top of NFS, accessing the Git data directly
via Rugged may be faster than going through than Gitaly. This merge
request introduces the feature flag `rugged_list_commits_by_oid` to
activate the Rugged method.
For one customer, we saw that ListCommitsByOid was the second highest
used endpoint that may be causing increased load.
|
|
This adds the backtrace to a table to show exactly where the Gitaly call
was made to make it easier to understand where the call originated.
This change also collapses the details in the same row to improve the
usability when there is a backtrace.
|
|
People who prefer plain text email also might prefer the raw job log
files. So include the link directly to there.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/56849
|
|
|
|
Restore "download repository path" feature, now with fixes and a feature flag
Closes gitlab-workhorse#218 and #24704
See merge request gitlab-org/gitlab-ce!27275
|
|
Using custom_action and recipient filtering
Add more generic filtering to user_ids_notifiable_on
Add changelog entry
Remove commented class
Method is no longer needed
Overloading no longer required
Filter by action just in case of custom notification level
Add participant check
Fix unexpected extra notification mails
Using custom_action and recipient filtering
Add more generic filtering to user_ids_notifiable_on
Add changelog entry
Remove commented class
Method is no longer needed
Overloading no longer required
Filter by action just in case of custom notification level
Fix comment
Add repond_to? checks
Reverted custom_action filtering
Enhanced output of should_email helper
Changed :watch to :participating for custom notifiable users
Change spec variable name
Enhanced participating check
These conditions are no longer needed
Fix custom notification handling for participating type
Participating level should include maintainers
Fixed add_guest notification
Fix successful pipeline notification
Refactoring: Use maintainer? method on team instead
Add spec for new_issue: true for a custom group setting
which should have lower prio than an available project setting
Clean up specs
|
|
Removes EE diffs for dropdown_value_collapsed.vue
Closes gitlab-ee#10083
See merge request gitlab-org/gitlab-ce!27367
|
|
|
|
'master'
Allow extra args for helm in Auto-DevOps
See merge request gitlab-org/gitlab-ce!26838
|
|
Set correct timestamps when creating past issues
Closes #58361
See merge request gitlab-org/gitlab-ce!27406
|
|
Test using Git 2.21
See merge request gitlab-org/gitlab-ce!27418
|
|
Replaced "View file" button with doc-text icon
Closes #59034
See merge request gitlab-org/gitlab-ce!27365
|
|
into 'master'
Update merge request widget to accommodate post-merge pipelines
See merge request gitlab-org/gitlab-ce!25983
|
|
This reverts commit 171818df0a72097aa1a804c8213666b3f66b0966.
|
|
Given Rails doesn't use the Git binary anymore, this shouldn't be a
problem.
|
|
Sets `system_note_timestamp` from `created_at`
|
|
Rewind iid on pipelines
Closes #59362
See merge request gitlab-org/gitlab-ce!26490
|
|
Update Node.js to 10.15.3 in CI template for Hexo
See merge request gitlab-org/gitlab-ce!25943
|
