Age | Commit message (Collapse) | Author |
|
|
|
Changed reference to Mattermost versions, so that it's clear which
menu navigation path applies.
|
|
Add docs for db_load_balancing metrics
See merge request gitlab-org/gitlab-ce!32044
|
|
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/66677
|
|
|
|
Improve documentation of stage, group, category, feature labels
See merge request gitlab-org/gitlab-ce!32053
|
|
|
|
Update the syntax of DAG example
See merge request gitlab-org/gitlab-ce!32137
|
|
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|
Currently, the DB migrations guide says that "you must" use non-blocking
operations (such as CREATE INDEX CONCURRENTLY), always.
But this does not make sense in cases of empty tables and leads to
splitting the work to multiple non-atomic
(with disable_ddl_transaction!) DB migrations.
To follow KISS principle, to have fewer DB migrations steps,
to have them atomic when it's possible and simplify deployment
and troubleshooting, the following exceptions were added
to the doc:
- index creation,
- index dropping,
- defining an FK,
- adding a column with DEFAULT,
|
|
Promote Label to Group Label via API endpoint
Closes #57657
See merge request gitlab-org/gitlab-ce!25218
|
|
Made it clear the pages are about feature flags,
and not documentation.
|
|
Clean up capitalization in /development /gitlab-basics and
/install
|
|
Also updates redirect text in /project-services
|
|
|
|
|
|
|
|
allow_bypass_two_factor configration dose not work with saml provider
|
|
Docs: Remove mention of Kubernetes service templates
See merge request gitlab-org/gitlab-ce!32093
|
|
|
|
|
|
|
|
|
|
|
|
Change from ruby mdl to node markdownlint, add
config file to root of project, delete old config
file, update exceptions, and fix one doc that
was didn't meet standards
|
|
Square and Angle bracket use causes kramdown warnings,
so changed or enclosed in backticks as needed
|
|
License Compliance now uses Python 3 by default.
See https://gitlab.com/gitlab-org/gitlab-ee/issues/12032
|
|
These need to be reset
|
|
Updated container scanning docs with a sample config
|
|
Document how GitLab stores passwords
See merge request gitlab-org/gitlab-ce!32077
|
|
related to https://gitlab.com/gitlab-org/gitlab-ce/issues/65422
|
|
|
|
Fix N+1 Gitaly calls in /api/v4/projects/:id/issues
See merge request gitlab-org/gitlab-ce!32171
|
|
|
|
The flag defaulted to true, so there's no change unless users turned it
off. Given there's a lack of issues regarding object pools, this should
be OK.
|
|
|
|
|
|
Remove duplicate text in health check doc
See merge request gitlab-org/gitlab-ce!32175
|
|
DB Load Balancing: Support SRV lookups
See merge request gitlab-org/gitlab-ce!32135
|
|
Update docs - SAST golang analyzer URLs are partially reliable
See merge request gitlab-org/gitlab-ce!32164
|
|
Add example usage of `SAST_EXCLUDED_PATHS`
See merge request gitlab-org/gitlab-ce!32120
|
|
|
|
|
|
|
|
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
|
|
|
|
With https://gitlab.com/gitlab-org/security-products/analyzers/gosec/merge_requests/18
we have added some basic URLs to our gosec analyzer, upgrading data from none to partially reliable
|
|
|
|
|