| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Extract duplicated code from two similar classes into a parent one.
|
|
Fix CE to EE differences in the qa/ directory
See merge request gitlab-org/gitlab-ce!32354
|
|
|
|
|
|
git-user-related local test failures
See merge request gitlab-org/gitlab-ce!31437
|
|
Remove usage of gitlab-shell gitlab-keys script
See merge request gitlab-org/gitlab-ce!32138
|
|
Fix snippets API not working with visibility level
Closes #66050
See merge request gitlab-org/gitlab-ce!32286
|
|
Remove unnecessary CSS class
Closes #66163
See merge request gitlab-org/gitlab-ce!32320
|
|
Standardize use of `content` parameter in snippets API
Closes #66673
See merge request gitlab-org/gitlab-ce!32296
|
|
into 'master'
Resolve "Issue due notification emails are threaded incorrectly"
See merge request gitlab-org/gitlab-ce!32325
|
|
Utilize the auto repair functionality of system checks.
|
|
|
|
This check is being removed from gitlab-shell as the file
is now being managed by gitlab-rails.
|
|
|
|
Simplify internal post receive messages
Closes #59808
See merge request gitlab-org/gitlab-ce!31640
|
|
Resolve "Migrate spec/javascripts/vue_mr_widget/components/states/mr_widget_auto_merge_failed_spec.js to Jest"
See merge request gitlab-org/gitlab-ce!32282
|
|
'56130-operations-environments-shows-incorrect-deployment-date-for-manual-deploy-jobs' into 'master'
Show correct deployment date for a manual job
Closes #56130
See merge request gitlab-org/gitlab-ce!32072
|
|
'62284-follow-up-from-resolve-api-to-get-all-project-group-members-returns-duplicates' into 'master'
Resolve "Follow-up from "Resolve "API to get all project/group members returns duplicates"""
Closes #62284
See merge request gitlab-org/gitlab-ce!28887
|
|
There was some confusion over whether `code` or `content` is the right
parameter for snippets. Internally, the database stores
`content`. However:
1. Project snippets use `code`. `code` gets remapped in `content` in
`lib/api/project_snippets.rb`.
2. Personal snippets use `content`.
To unify these APIs, allow an alias of `content` to work for project
snippets.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/66673
|
|
When a restricted visibility level of `private` is set in the instance,
creating a snippet with the `visibility` level would always fail.
This happened because:
1. `params[:visibility]` was a string (e.g. "public")
2. `CreateSnippetService` and `UpdateSnippetService` only looked
at `params[:visibility_level]`, which was `nil`.
To fix this, we:
1. Make `CreateSnippetService` look at the newly-built
`snippet.visibility_level`, since the right value is assigned by the
`VisibilityLevel#visibility=` method.
2. Modify `UpdateSnippetService` to handle both `visibility_level` and
`visibility` parameters.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/66050
|
|
Add warnings to performance bar response
See merge request gitlab-org/gitlab-ce!31054
|
|
It should not be a start to a new thread but rather
a reply to an existing thread
|
|
Instead of sending varied data to Gitaly, and making Gitaly construct
various messages, build the messages first and have Gitaly print
either basic messages or alert messages, in the order they come.
Depends on https://gitlab.com/gitlab-org/gitaly/merge_requests/1410
|
|
|
|
- Extract MR fields for notes into a separate serializer
- Check if pipelines are empty via count
|
|
Resolve "Migrate spec/javascripts/vue_shared/components/file_icon_spec.js to Jest"
See merge request gitlab-org/gitlab-ce!32278
|
|
Persists if a board list is collapsed for each user.
|
|
|
|
|
|
|
|
This key is useful to reduce the amount of logic needed on the frontend:
if `has_warnings` is true, then the frontend knows that the request in
question has warnings for some metric.
|
|
For each DetailedView subclass, we add a `warnings` array to:
1. The top-level response.
2. Each individual call under the `details` key.
We use the `.thresholds` hash on the DetailedView to determine what's a
warning. If that hash is empty (the default), then the warnings array
will always be empty.
|
|
This ensures the InjectEnterpriseEditionModule cop is able to detect the
prepend patterns used in the qa/ directory. Previously it would not
detect them as all EE QA modules reside in QA::EE, and not the top-level
EE namespace.
|
|
Remove csslab
Closes #66661
See merge request gitlab-org/gitlab-ce!32330
|
|
A new param with_security_reports was added to
GET /groups/:id/projects API and the code to
support this logic in GroupProjectsFinder and
Project model. Also, a DB index was added to
ci_job_artifacts table to speed up the search
of security reports artifacts for projects
|
|
This change sets NOT NULL constraint to users.private profile.
closes https://gitlab.com/gitlab-org/gitlab-ce/issues/57538
|
|
Only display time if the job has deployed
Update JS tests for displaying job deployment time
Simplify boolean check in deployedDate
|
|
Add rubocop check for be success
See merge request gitlab-org/gitlab-ce!32091
|
|
Makes LFS object link process OIDs in batches
Closes #66274
See merge request gitlab-org/gitlab-ce!32268
|
|
|
|
- local tests that assume certain parameters to queries from
QueryRecorder fail. These same tests don't fail in the runners,
and I can't tell why. This fixes the local failures
|
|
Add changelog entry
Remove unnecessary test checking for form value
Translations updated for gitlab.pot
Use proper format on changelog entry
|
|
Change the way totalNotes is calculated
See merge request gitlab-org/gitlab-ce!32191
|
|
Fix moving issues API failing when text includes commit URLs
Closes #66666
See merge request gitlab-org/gitlab-ce!32317
|
|
|
|
When a issue is moved from one project to another, all associated
Markdown text is rewritten in the context of the new project. If the
note contained a link to a commit URL, `CommitRewriter#rewrite` would
fail because `Commit#link_reference_pattern` would match `nil` `commit`
values in the HTML generated from the Markdown. These `nil` values were
passed along to `Project#commits_by` because `Commit#reference_valid?`
was always returning `true`.
To prevent this issue from happening, we tighten up the check for
`Commit#reference_valid?` to look for valid SHA values.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/66666
|
|
Improve specs output readability by replacing
`it_behaves_like` with `include_examples`
in `BeSuccessMatcher`
|
|
This also restructures how and where the configuration for
Snowplow lives.
|
|
|
