Age | Commit message (Collapse) | Author |
|
Split into user and administrator docs:
- administration/issue_closing_pattern.md
- user/project/issues/automatic_issue_closing.md
[ci skip]
|
|
|
|
[ci skip]
|
|
Add optional 'author' param when making commits
This fulfills https://gitlab.com/gitlab-org/gitlab-ce/issues/20789 by adding the ability to specify a user's ID to be used as the author of a commit.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/20789
See merge request !5822
|
|
Lets the user choose a namespace and name on Github imports
Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/14971
See merge request !5728
|
|
LFS support for ssh enabled
## What does this MR do?
This is follow-up after https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6043 which is falsely shown as merged due to: https://gitlab.com/gitlab-org/gitlab-ce/issues/22334
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the 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?
See merge request !6413
|
|
|
|
and/or name for a project.
- Fixed and added specs.
- Added different namespace options depending on user privilages
- Updated docs.
|
|
Use gitlab-workhorse 0.8.2
Fixes rejected API git archive extensions; improves Sentry errors.
https://gitlab.com/gitlab-org/gitlab-workhorse/blob/master/CHANGELOG
See merge request !6388
|
|
|
|
Allow to set request_access_enabled for groups and projects using API
Closes #20978
See merge request !6359
|
|
|
|
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6043"
This reverts commit 6d43c95b7011ec7ec4600e00bdc8df76bb39813c.
|
|
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
|
|
[ci skip]
|
|
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6043
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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
|
|
[ci skip]
|
|
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
|
|
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
|
|
|
|
|
|
|
|
|
|
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
|
|
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
|
|
|
|
Fixes rejected API git archive extensions; improves Sentry errors.
|
|
Integer migration style
See merge request !6334
|
|
|
|
|
|
Groups can enable/disable LFS, but this setting can be overridden at the project level. Admin only
|
|
|
|
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
|
|
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
|
|
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
|
|
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|
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
|
|
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
|
|
|
|
[ci skip]
|
|
locally
|
|
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
|
|
|