| Age | Commit message (Collapse) | Author |
|---|
|
Ci Project migrate
- This doesn't migrate: allow_git_fetch, coverage_regex, timeout. Since this are project configuration settings I would propose to migrate them to `.gitlab-ci.yml`.
- This requires offline migrations.
- It simplifies database models making all CI objects to be attached to: Project.
- It removes Ci::Project, but makes /ci/projects working by adding method: Project.find_by_ci_id for backward compatibility (badges, triggers).
- We should add default `timeout` to Application Settings.
- It misses specs.
- It is based on ci-services-migrate for now.
- It removes CI events.
- It removes administrator CI projects overview.
- It removes CI application settings.
In 8.4 or 8.5 we can remove redundant tables and columns.
See merge request !1987
|
|
[ci skip]
Closes https://github.com/gitlabhq/gitlabhq/issues/9904
|
|
Closes #3649
[ci skip]
|
|
|
|
|
|
|
|
Fix typos in all docs
|
|
|
|
Fix typos in integration docs
[ci skip]
See merge request !1999
|
|
Update init script only once
The init script is already being updated in section 6.
See merge request !2038
[ci skip]
|
|
Remove default_branch from project API creation documentation
The docs erroneously included `default_branch` as an option in project creation, but this field does not make sense because a new project has an empty repo with no branches.
Closes #3937
See merge request !2034
|
|
The init script is already being updated in section 6.
|
|
Remove the prepended v on GitLab Workhorse upgrade doc
Fix for https://gitlab.com/gitlab-org/gitlab-workhorse/issues/4
See merge request !2020
|
|
Merge when build succeeds
### What does this MR do?
Adds a button to a MR when the build/ci is running so it can be merged when/if the build is successfull.
### Are there points in the code the reviewer needs to double check?
English spelling and whether or not the grammer is correct.
### Why was this MR needed?
When you expect its all good, and don't want to revisit the current MR it can be accepted allready.
### What are the relevant issue numbers / Feature requests?
Fixes #2640 -- although `Merge if green` is replaced with `Merge when the build succeeds` the general idea is the same.
### Screenshots (if relevant)
### Further considerations
What if there are minor things needed solving, e.g. Rubocop, the current implementation will reset the approved status of the MR. It might be a consideration keep the approval for team member, or even guests. This would require an extra option in the Admin screen, though might add extra value.
#### TODO
- [x] Docs
- [x] Specs
/cc @DouweM @rspeicher
See merge request !1729
|
|
Introduce CI documentation for services and languages
This introduces guide for PHP, a bunch of services (databases) and cleans up some docker references.
With this there are bunch of example projects in https://gitlab.com/groups/gitlab-examples.
/cc @JobV @axil
See merge request !1917
|
|
# Conflicts:
# app/controllers/projects/merge_requests_controller.rb
# config/routes.rb
|
|
has no branches to start.
Closes #3937
|
|
Update documentation about automatic issue closing
RE !1933
See merge request !2000
|
|
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/1917#note_2833978
|
|
|
|
# Conflicts:
# app/views/projects/merge_requests/widget/_heading.html.haml
# app/views/projects/merge_requests/widget/open/_accept.html.haml
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
UI: Add "New X" buttons to dashboard and group issue, MR and milestone indexes
# To do
- [x] Use searchable dropdown since dashboard/group can have a lot of projects. Use select2?
## Before
## After
As you can see, for milestones, groups are listed as well as we can now easily create group milestones.
Fixes #3544 and https://dev.gitlab.org/gitlab/gitlabhq/issues/2581
See merge request !1968
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
