summaryrefslogtreecommitdiff
path: root/doc
Commit message (Collapse)AuthorAgeFilesLines
* Edit limit textdocs/edit-limit-textEvan Read2019-08-282-8/+10
|
* Merge branch 'mk/remove-jwt-from-rate-limit-docs' into 'master'Evan Read2019-08-282-1/+5
|\ | | | | | | | | Note CI token exception to JWT requests in rate limit docs See merge request gitlab-org/gitlab-ce!32168
| * Note some JWT requests aren't rate limitedmk/remove-jwt-from-rate-limit-docsMichael Kozono2019-08-232-1/+5
| |
* | Remove eks from adding an existing cluster sectionDaniel Gruesso2019-08-281-1/+1
| |
* | Resolving minor formatting issues in gitlab-basicsMarcel Amirault2019-08-283-4/+2
| |
* | Update group permissions table documentationEugenia Grieff2019-08-281-18/+20
| |
* | Change reference to Mattermost versions.Russell Dickenson2019-08-281-2/+7
| | | | | | | | | | Changed reference to Mattermost versions, so that it's clear which menu navigation path applies.
* | Merge branch 'load-balancing-prometheus' into 'master'Evan Read2019-08-271-1/+10
|\ \ | | | | | | | | | | | | Add docs for db_load_balancing metrics See merge request gitlab-org/gitlab-ce!32044
| * | Add docs for db_load_balancing metricsload-balancing-prometheusThong Kuah2019-08-271-1/+10
| | |
* | | Remove trailing whitespace from project snippets API docssh-fix-docs-lint-snippetsStan Hu2019-08-271-2/+2
| | | | | | | | | | | | Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/66677
* | | Add example requests for snippets APIRainer Kern2019-08-271-0/+58
| | |
* | | Merge branch 'docs-document-category-labels' into 'master'Achilleas Pipinellis2019-08-273-131/+194
|\ \ \ | | | | | | | | | | | | | | | | Improve documentation of stage, group, category, feature labels See merge request gitlab-org/gitlab-ce!32053
| * | | Introduce facet labelsdocs-document-category-labelsRémy Coutable2019-08-271-0/+18
| | | | | | | | | | | | | | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
| * | | Improve documentation of stage, group, category, feature labelsRémy Coutable2019-08-273-135/+180
| | | | | | | | | | | | | | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* | | | Removes trailing whitespace to fix lintingEvan Read2019-08-271-5/+5
| | | |
* | | | Merge branch 'docs-update-needs-example' into 'master'Kamil Trzciński2019-08-271-4/+4
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | Update the syntax of DAG example See merge request gitlab-org/gitlab-ce!32137
| * | | | Update syntax of needs exampledocs-update-needs-exampleAlexander Tanayno2019-08-231-4/+4
| | | | |
* | | | | Migrations guide: use atomic steps, when possibleMayra Cabrera2019-08-272-44/+99
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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,
* | | | | Merge branch '57657-promote-label-to-group-label-via-api-endpoint' into 'master'Sean McGivern2019-08-271-0/+34
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Promote Label to Group Label via API endpoint Closes #57657 See merge request gitlab-org/gitlab-ce!25218
| * | | | | Update docs targeting 12.3Robert Schilling2019-08-261-1/+1
| | | | | |
| * | | | | Move promote to put and add more specsRobert Schilling2019-08-261-2/+2
| | | | | |
| * | | | | Add docs and first specsRobert Schilling2019-08-261-0/+34
| | |/ / / | |/| | |
* | | | | Update index of feature flagsSeth Berger2019-08-271-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | Made it clear the pages are about feature flags, and not documentation.
* | | | | Update capitalization in /dev docsMarcel Amirault2019-08-2722-95/+93
| | | | | | | | | | | | | | | | | | | | | | | | | Clean up capitalization in /development /gitlab-basics and /install
* | | | | Update capitalization in /integrations and /raketasksMarcel Amirault2019-08-2735-79/+82
| | | | | | | | | | | | | | | | | | | | Also updates redirect text in /project-services
* | | | | [#2838] add cache override explanationJace Bennest2019-08-271-0/+23
| | | | |
* | | | | Update `only` `chat` statement to correct singular formDaniel Gruesso2019-08-271-1/+1
| | | | |
* | | | | Add missing blank line to omniauth docMarcel Amirault2019-08-271-0/+1
| | | | |
* | | | | Update docs and comments about saml with allow_bypass_two_factordodocat2019-08-271-0/+20
| | | | | | | | | | | | | | | | | | | | allow_bypass_two_factor configration dose not work with saml provider
* | | | | Merge branch 'docs-no-more-k8s-service-template' into 'master'Evan Read2019-08-271-3/+2
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | Docs: Remove mention of Kubernetes service templates See merge request gitlab-org/gitlab-ce!32093
| * | | | | Remove mention of Kubernetes service templatesdocs-no-more-k8s-service-templateThong Kuah2019-08-221-3/+2
| | | | | | | | | | | | | | | | | | This has since been removed
* | | | | | Update doc/api/events.mdAlexis Sánchez2019-08-271-6/+6
| | | | | |
* | | | | | CI Yaml configuration docs for using job rulesdrew2019-08-271-0/+120
| |_|_|/ / |/| | | |
* | | | | Added note that Multiple Issue Boards moved tiers.Russell Dickenson2019-08-263-22/+14
| | | | |
* | | | | Add documentation about Gitaly concurrency limiterJacob Vosmaer2019-08-261-0/+41
| | | | |
* | | | | Change docs markdown linterMarcel Amirault2019-08-265-23/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | | | Add backticks and remove square bracketsMarcel Amirault2019-08-263-181/+170
| | | | | | | | | | | | | | | | | | | | | | | | | Square and Angle bracket use causes kramdown warnings, so changed or enclosed in backticks as needed
* | | | | License Compliance defaults to Python 3Fabien Catteau2019-08-261-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | License Compliance now uses Python 3 by default. See https://gitlab.com/gitlab-org/gitlab-ee/issues/12032
* | | | | ci_builds also has encrypted tokensBill Bagdon2019-08-261-0/+23
| | | | | | | | | | | | | | | | | | | | These need to be reset
* | | | | Updated container scanningSeth Berger2019-08-261-1/+31
| | | | | | | | | | | | | | | | | | | | Updated container scanning docs with a sample config
* | | | | Merge branch 'docs-password-storage' into 'master'Achilleas Pipinellis2019-08-262-0/+14
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | Document how GitLab stores passwords See merge request gitlab-org/gitlab-ce!32077
| * | | | | Improve readability of salting descriptiondocs-password-storageChristiaan Conover2019-08-221-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add a comma in the final sentence of the description of salting, to improve the readability of what's being said.
| * | | | | Fix a typo in the section on stretchingChristiaan Conover2019-08-221-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | Correct a typo in the description of how passwords are stretched.
| * | | | | Fix link syntax typoChristiaan Conover2019-08-211-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fix a missing parentheses in the markdown for a link caused by the URL containing parentheses.
| * | | | | Document how GitLab stores passwordsChristiaan Conover2019-08-212-0/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Provide details on how GitLab stores passwords, including hashing, stretching, and salting. This was driven by a customer asking for this information for a security compliance audit report.
* | | | | | Improve Gitaly path detailsBen Bodenmiller2019-08-261-9/+13
| | | | | | | | | | | | | | | | | | | | | | | | related to https://gitlab.com/gitlab-org/gitlab-ce/issues/65422
* | | | | | Add Documentation for `line-chart`Miguel Rincon2019-08-261-1/+1
| | | | | |
* | | | | | Merge branch 'sh-fix-nplusone-issues' into 'master'Mayra Cabrera2019-08-261-1/+0
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fix N+1 Gitaly calls in /api/v4/projects/:id/issues See merge request gitlab-org/gitlab-ce!32171
| * | | | | | Fix N+1 Gitaly calls in /api/v4/projects/:id/issuessh-fix-nplusone-issuesStan Hu2019-08-231-1/+0
| | |_|_|_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | | | | Remove the object pools feature flagZeger-Jan van de Weg2019-08-262-31/+5
| |_|_|/ / |/| | | | | | | | | | | | | | | | | | | | | | | | 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.