Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
path: root/doc
AgeCommit message (Collapse)Author
2016-09-19Merge branch 'fix/import-export-db-errors' into 'master' Rémy Coutable
Fix import/export database errors Fixes protected branches errors when importing a project including them Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/21295 Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/21799 See merge request !6099
2016-09-19Fix environments handlingKamil Trzcinski
2016-09-19Small refactor of review apps docsAchilleas Pipinellis
2016-09-19Cleanup changesKamil Trzcinski
2016-09-19Added documentation about dynamic environmentsKamil Trzcinski
2016-09-19Fixed label color issue and added Import/Export versioning tableJames Lopez
2016-09-18Merge branch 'doc/download-latest-artifact' into 'master' Achilleas Pipinellis
Document how to download the latest build artifacts ## What does this MR do? Document how to download the latest build artifacts. Closes gitlab-org/gitlab-ce#22273 See merge request !6401
2016-09-18Document how to download the latest build artifactsAchilleas Pipinellis
[ci skip]
2016-09-18Merge branch 'update-github-doc-page' into 'master' Achilleas Pipinellis
Update GitHub importer documentation to reflect current importer state ## What does this MR do? Update the Github importer documentation to reflect the current importer state. ## What are the relevant issue numbers? https://gitlab.com/gitlab-org/gitlab-ee/issues/904 ## Does this MR meet the acceptance criteria? - [X] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md) See merge request !5987
2016-09-18Merge branch 'patch-3' into 'master' Achilleas Pipinellis
improve wording on build and push images using GitLab CI docs ## What does this MR do? Improve wording on build and push images using GitLab CI docs ## Are there points in the code the reviewer needs to double check? No ## Why was this MR needed? Poor wording ## Does this MR meet the acceptance criteria? - [ ] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added - [X] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md) - [ ] API support added - Tests - [ ] Added for this feature/bug - [ ] All builds are passing - [ ] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides) - [X] Branch has no merge conflicts with `master` (if you do - rebase it please) - [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits) See merge request !6001
2016-09-18Clarify why GH integration is the preferred importing methodAchilleas Pipinellis
2016-09-18Refactor GitHub importing documentationAchilleas Pipinellis
2016-09-18Update GitHub importer documentation to reflect current importer stateDouglas Barbosa Alexandre
2016-09-18Formatting fix in doc/ci/examples/README.mdsknebel
2016-09-17Merge branch 'patch-3' into 'master' Achilleas Pipinellis
docs: fix typo, it should refer to `domain_blacklist_enabled` setting ## What does this MR do? fix the documentation ## Are there points in the code the reviewer needs to double check? N/A ## Why was this MR needed? typo fix ## What are the relevant issue numbers? N/A ## Screenshots (if relevant) N/A ## Does this MR meet the acceptance criteria? yes, it's just a typo fix in the documentation without any code or business logic changes See merge request !5899
2016-09-17Merge branch 'patch-3' into 'master' Achilleas Pipinellis
Document IAM Profile AWS S3 configuration key. ## What does this MR do? Document additional parameters available to the backup rake job configuration. ## Are there points in the code the reviewer needs to double check? Probably not. ## Why was this MR needed? Un-documented configuration options ## What are the relevant issue numbers? #12756 ## Does this MR meet the acceptance criteria? - [ ] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added - [X] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md) - [ ] API support added - Tests - [ ] Added for this feature/bug - [ ] All builds are passing - [ ] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides) - [ ] Branch has no merge conflicts with `master` (if you do - rebase it please) - [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits) See merge request !5910
2016-09-16Fix API notes endpoint when posting only emojiZ.J. van de Weg
2016-09-16Merge branch 'integer_migration_style' into 'master' Yorick Peterse
Integer migration style See merge request !6334
2016-09-16Add support for column limits in add_column_with_defaultDrew Blessing
2016-09-15Syntax fixes and better tests for helper methods. Updated docs.Patricio Cano
2016-09-15Added group-specific setting for LFS.Patricio Cano
Groups can enable/disable LFS, but this setting can be overridden at the project level. Admin only
2016-09-15Merge branch 'ci-quick-start-doc-improvement' into 'master' Achilleas Pipinellis
doc/ci/quick_start/README: improve sentence about link to a Lint tool ## What does this MR do? It improves the `doc/ci/quick_start/README.md` documentation. ## Are there points in the code the reviewer needs to double check? The reviewer can check that there is no more **CI settings** menu and that the Lint tool can be accessed under **Pipelines > Pipelines** and **Pipelines > Builds**. ## Why was this MR needed? Because the CI quick start documentation was not correct. ## Screenshots (if relevant) ## Does this MR meet the acceptance criteria? It is not a code change so I don't think the below criteria are relevant. - [ ] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added - [ ] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md) - [ ] API support added - Tests - [ ] Added for this feature/bug - [ ] All builds are passing - [ ] Conform by the [merge request performance guides](http://docs.gitlab.com/ce/development/merge_request_performance_guidelines.html) - [ ] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides) - [ ] Branch has no merge conflicts with `master` (if you do - rebase it please) - [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits) ## What are the relevant issue numbers? I didn't check if there was an issue for this. See merge request !6301
2016-09-15Merge branch 'user-permission-doc-fix' into 'master' Achilleas Pipinellis
doc/user/permissions: update option and menu names ## What does this MR do? This fixes `doc/user/permissions.md` documentation. ## Are there points in the code the reviewer needs to double check? The reviewer can check that the name of the option is now **Public pipelines** and that this option is in **Project Settings > CI/CD Pipelines**. ## Why was this MR needed? Because the previous name of the option and of the menu had not been updated in `doc/user/permissions.md` when they were changed. ## Screenshots (if relevant) ## Does this MR meet the acceptance criteria? This is a documentation only MR, so I don't think it needs to pass all these acceptance criteria. - [ ] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added - [ ] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md) - [ ] API support added - Tests - [ ] Added for this feature/bug - [ ] All builds are passing - [ ] Conform by the [merge request performance guides](http://docs.gitlab.com/ce/development/merge_request_performance_guidelines.html) - [ ] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides) - [ ] Branch has no merge conflicts with `master` (if you do - rebase it please) - [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits) ## What are the relevant issue numbers? I don't know of any issue number. See merge request !6302
2016-09-14Merge branch 'document-checkout-mr-from-forks-locally' into 'master' Job van der Voort
Document the fact that merge requests from forks can be checked out locally As pointed out by @JobV, our documentation doesn't clearly state that you can checkout a merge request from a fork locally. See merge request !6324
2016-09-14Update the 8.11 to 8.12 update documentation to use gitlab-shell 3.5.0Rémy Coutable
Signed-off-by: Rémy Coutable <remy@rymai.me>
2016-09-13Merge branch 'feature/builds-register-change-404-to-204' into 'master' Rémy Coutable
Change response for /ci/api/v1/builds/register.json from 404 to 204 ## What does this MR do? To check if there are new builds scheduled for a runner, runner is sending `POST /ci/api/v1/builds/register.json` requests. If there is a build then a `200` response with build data is returned. However if there is no builds scheduled for this runner it receives a `404 Not Found` response. This may end with a lot of `404 Not Found` lines in logs that are an expected behavior (please read #14445 for a reference). Since `v1.0.1` version GitLab Runner is ready to receive a `204 No Content` response in case of no builds. This MR adds a support for this status code for each Runner's version that can be determined while handling `POST /ci/api/v1/builds/register.json` request. ## Are there points in the code the reviewer needs to double check? Specs in `spec/requests/ci/api/builds_spec.rb` ## Does this MR meet the acceptance criteria? - [x] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added - [x] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md) - [ ] ~~API support added~~ - Tests - [x] Added for this feature/bug - [x] All builds are passing - [ ] ~~Conform by the [merge request performance guides](http://docs.gitlab.com/ce/development/merge_request_performance_guidelines.html)~~ - [x] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides) - [x] Branch has no merge conflicts with `master` (if you do - rebase it please) - [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits) ## What are the relevant issue numbers? Fixes #14445 See merge request !6225
2016-09-13Merge branch '20780-import-github-release-notes' into 'master' Robert Speicher
Import GitHub release notes ## Why was this MR needed? Release notes aren't currently migrated over when importing from GitHub ## What are the relevant issue numbers? #20780 See merge request !5981
2016-09-13Fix a typo in documentationTomasz Maczukin
2016-09-13Update API documentationTomasz Maczukin
[ci skip]
2016-09-13Document the fact that merge requests from private forks can be checked out ↵Rémy Coutable
locally
2016-09-13Merge branch 's3-region' into 'master' Achilleas Pipinellis
Include region in S3 configuration - [x] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md) See https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5336 See merge request !5896
2016-09-13include region for source installation Chris Wilson
2016-09-13Import GitHub release notesAndrew Smith
# Conflicts: # lib/gitlab/github_import/importer.rb
2016-09-12Merge branch 'document-custom-event-tracking' into 'master' Achilleas Pipinellis
Document how to track custom events ## What does this MR do? This documents how one can track custom events. ## Are there points in the code the reviewer needs to double check? Spelling, etc. ## Why was this MR needed? This wasn't documented. ## Screenshots (if relevant) ## Does this MR meet the acceptance criteria? - [x] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md) - [ ] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides) - [x] Branch has no merge conflicts with `master` (if you do - rebase it please) - [x] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits) ## What are the relevant issue numbers? https://gitlab.com/gitlab-org/gitlab-ce/issues/22070 See merge request !6310
2016-09-12Merge branch 'issue_21825' into 'master' Rémy Coutable
Add information about user and manual build start to runner as variables Closes #21825 See merge request !6201
2016-09-12Document how to track custom eventsYorick Peterse
Fixes gitlab-org/gitlab-ce#22070 [ci skip]
2016-09-12doc/user/permissions: update option and menu namesChristian Couder
It looks like the option is now called **Public pipelines** and the menu item is now **Project Settings > CI/CD Pipelines**.
2016-09-12doc/ci/quick_start/README: improve sentence about link to a Lint tool Christian Couder
The link is now a button under **Pipelines > Pipelines** and **Pipelines > Builds**. There is no more **CI settings** menu.
2016-09-09Add notification_settings API callsMarc Siegfriedt
Use NotificationSetting::EMAIL_EVENTS for params
2016-09-09Merge branch 'workhorse-0.8.1' into 'master' Robert Speicher
Use gitlab-workhorse 0.8.1 Adds Sentry support in gitlab-workhorse. See merge request !6283
2016-09-09Use gitlab-workhorse 0.8.1Jacob Vosmaer
This adds (basic) Sentry support.
2016-09-09Merge branch 'zj-update-ci-examples-doc' into 'master' Achilleas Pipinellis
Minor update on CI docs examples cc @ayufan @markpundsack Commit message: > Triggered by gitlab-org/gitlab-ci-yml#1 I've investigated how this is organized so far and did a minor clean up. In my opinion we should just keep a list of up to date blog posts in the docs and examples should be included in gitlab-org/gitlab-ci-yml. This reduces the number of projects and docs pages one has to look for information. See merge request !5806
2016-09-09Merge branch 'gitlab-workhorse-safeties' into 'master' Jacob Vosmaer (GitLab)
Security and safety improvements for gitlab-workhorse integration Companion to https://gitlab.com/gitlab-org/gitlab-workhorse/merge_requests/60 - Use a custom content type when sending data to gitlab-workhorse - Verify (using JWT and a shared secret on disk) that internal API requests came from gitlab-workhorse This will allow us to build features in gitlab-workhorse that require more trust, and protect us against programming mistakes in the future. This is designed so that no action is required for installations from source. For omnibus-gitlab we need to add code that manages the shared secret. See merge request !5907
2016-09-09Minor update on CI docs examplesZ.J. van de Weg
Triggered by gitlab-org/gitlab-ci-yml#1 I've investigated how this is organized so far and did a minor clean up. In my opinion we should just keep a list of up to date blog posts in the docs and examples should be included in gitlab-org/gitlab-ci-yml. This reduces the number of projects and docs pages one has to look for information. [ci skip]
2016-09-09Add information about user and manual build start to runner as variablesSergey Gnuskov
2016-09-08Merge branch 'dz-mr-version-compare' into 'master' Douwe Maan
Allow compare merge request versions ## What does this MR do? Add new functionality to the merge request page. It allows you easily compare merge request versions in one click. ## Are there points in the code the reviewer needs to double check? ## Why was this MR needed? To improve code review experience. ## Screenshots (if relevant) See discussion ## Does this MR meet the acceptance criteria? - [x] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added - [x] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md) - [x] ~~API support added~~ - Tests - [x] Added for this feature/bug - [x] All builds are passing - [x] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides) - [x] Branch has no merge conflicts with `master` (if you do - rebase it please) - [x] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits) ## What are the relevant issue numbers? https://gitlab.com/gitlab-org/gitlab-ce/issues/13570 See merge request !6127
2016-09-08Use gitlab-workhorse 0.8.0Jacob Vosmaer
2016-09-07Merge branch 'patch-5' into 'master' Rémy Coutable
Fix: Switch sample values for $CI_SERVER_REVISION and $CI_SERVER_VERSION. See the general Documentation guidelines http://docs.gitlab.com/ce/development/doc_styleguide.html. ## What does this MR do? There is a sample in this document showing the possible values of the predefined CI variables. Those of **CI_SERVER_REVISION** and **CI_SERVER_VERSION** were mixed up. I fixed that. See merge request !6243
2016-09-07Merge branch '15571-api-for-ci-lint' into 'master' Rémy Coutable
API for CI Lint ## What does this MR do? Add API for CI Lint. Can check if `.gitlab-ci.yml` content is valid. ## What are the relevant issue numbers? Closes #15571 ## Does this MR meet the acceptance criteria? - [x] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added - [x] API support added - [x] Documentation - Tests - [x] Added for this feature/bug - [x] All builds are passing cc @ubudzisz @grzesiek @yorickpeterse See merge request !5953
2016-09-07Merge branch 'master' into 'master' Rémy Coutable
Issue #21440: Small fix to curl example for adding member to project ## What does this MR do? Two lines changed in docs to move the user_id field out of the url and onto the query string ## Why was this MR needed? Issue #21440 reported under Issues. The documentation example for adding members to a project had a slight problem. ## What are the relevant issue numbers? Closes #21440. See merge request !6236
generated by cgit v1.2.3 (git 2.25.1) at 2024-08-17 14:50:30 +0300