| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Adds a slash command in slach for closing issues. See
https://docs.gitlab.com/ee/integration/slash_commands.html
for documentation on the wider feature set.
|
|
|
|
| |
This reverts commit 0eff75fa2b6691b6fba31fcc2842f51debd249a9.
|
|\
| |
| |
| |
| | |
Remove usage of gitlab-shell gitlab-keys script
See merge request gitlab-org/gitlab-ce!32138
|
| |
| |
| |
| | |
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.
|
| | |
|
|\ \
| |/
|/|
| |
| |
| |
| | |
Standardize use of `content` parameter in snippets API
Closes #66673
See merge request gitlab-org/gitlab-ce!32296
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|\ \
| |/
|/|
| |
| |
| |
| | |
Simplify internal post receive messages
Closes #59808
See merge request gitlab-org/gitlab-ce!31640
|
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|\ \
| |/
|/|
| |
| | |
Add warnings to performance bar response
See merge request gitlab-org/gitlab-ce!31054
|
| |
| |
| |
| |
| |
| | |
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.
|
| | |
|
| |
| |
| |
| | |
The original name has been deprecated
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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 also restructures how and where the configuration for
Snowplow lives.
|
| | |
|
| |
| |
| |
| | |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|/
|
|
| |
(cherry picked from commit 897a9d308db46b620b738b98f2b0e5630ac7d2dd)
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
'65312-use-group-labels-instead-of-legacy-team-labels-for-danger-picking-test-reviewers' into 'master'
Detect the new stage labels in `Gitlab::Danger::Teammate`
Closes #65312
See merge request gitlab-org/gitlab-ce!32261
|
| |
| |
| |
| | |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|\ \
| |/
|/|
| |
| |
| |
| | |
Add nil check for Gitlab.config.prometheus
Closes #13806
See merge request gitlab-org/gitlab-ce!32201
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Promote Label to Group Label via API endpoint
Closes #57657
See merge request gitlab-org/gitlab-ce!25218
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Resolve "Store deploy tokens encrypted"
Closes #63502
See merge request gitlab-org/gitlab-ce!30679
|
| | | | |
|
| | | | |
|
|/ / /
| | |
| | |
| | | |
allow_bypass_two_factor configration dose not work with saml provider
|
| | |
| | |
| | |
| | | |
This reverts merge request !31826
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
This also restructures how and where the configuration for
Snowplow lives.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Fix N+1 Gitaly calls in /api/v4/projects/:id/issues
See merge request gitlab-org/gitlab-ce!32171
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is a follow-up from
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/31938.
In GitLab 9.0,
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/9661 removed the
`subscribed` flag from the API when the user requested a list of issues
or merge requests since calculating this value triggers extensive
Markdown processing.
In GitLab 12.0 via a4fbf39e, we accidentally reintroduced this
performance regression by changing `IssueBasic` to `Issue` in
`entities.rb`. This showed up as a Gitaly N+1 issue since the Markdown
processing would attempt to extract a commit if it detected a regex that
matched a commit.
We restore the prior behavior by once again removing the `subscribed`
flag for the bulk list of issues and merge requests and add a test to
ensure they aren't reintroduced.
Relates to https://gitlab.com/gitlab-org/gitlab-ce/issues/66202
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The `GraphQL::Function` has been deprecated in
favor of resolvers.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Code Review Usage Ping for Create SMAU
|
| |/ /
|/| | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
DB Load Balancing: Support SRV lookups
See merge request gitlab-org/gitlab-ce!32135
|
| | | | |
|
| |_|/
|/| |
| | |
| | | |
- Also add helper to undo rename_column_concurrently.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- When renaming a column concurrently, drop any existing trigger before
attempting to create a new one.
When running migration specs multiple times (as it happens during
local development), the down method of previous migrations are called.
If any of the called methods contains a call to
rename_column_concurrently, a trigger will be created and not removed.
So, the next time a migration spec is run, if the same down method is
executed again, it will cause an error when attempting to create the
trigger (since it already exists). Dropping the trigger if it already
exists will prevent this problem.
|
| | |
| | |
| | |
| | | |
Add to the service and migration both.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Resolve "Use Visual Review Tools NPM package"
See merge request gitlab-org/gitlab-ce!32159
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Remove the visual review toolbar code
in favor of using the NPM package.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Allow users to read pipelines for public projects
with public builds enabled without providing an access token.
|