| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| |
| |
| | |
Add note about only 20 commits being included in push payload
See merge request gitlab-org/gitlab-ce!16149
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
Update irker documentation to mention an irker bug with key-protected channels.
See merge request gitlab-org/gitlab-ce!16274
|
| | | |
| | |
| | |
| | | |
Signed-off-by: Mattia Rizzolo <mattia@debian.org>
|
| |\ \ \
| |/ /
| | |
| | | |
* master: (114 commits)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When a project uses fast-forward merging strategy user has
to rebase MRs to target branch before it can be merged.
Now user can do rebase in UI by clicking 'Rebase' button
instead of doing rebase locally.
This feature was already present in EE, this is only backport
of the feature to CE. Couple of changes:
* removed rebase license check
* renamed migration (changed timestamp)
Closes #40301
|
| | | |
| | |
| | |
| | |
| | |
| | | |
States this service was deprecated on 10.3 and his behavior depends on
the kubernetes service status. Also includes a link for the release post
for more information.
|
| |/ /
| |
| |
| |
| | |
We need to bump import/export version because we introduced a new
object's hierarchy that is not backwards compatible.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
into 'master'
Updates documentation for Prometheus and Kubernetes integration
Closes #41432
See merge request gitlab-org/gitlab-ce!16156
|
| | |/ |
|
| | | |
|
| | | |
|
| |/ |
|
| |\
| |
| |
| |
| |
| |
| | |
Add note about using the term GPG for all related implementations
Closes #36970
See merge request gitlab-org/gitlab-ce!14887
|
| | |
| |
| |
| | |
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/36970
|
| |\ \
| |/
|/|
| |
| | |
Fix prometheus arg in prometheus.yml
See merge request gitlab-org/gitlab-ce!16075
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |/
|
|
|
|
| |
- move the section
- replace identifiers with inline links
- update settings (General settings > Advanced settings)
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
Add commit diff discussion in merge request context documentation
See merge request gitlab-org/gitlab-ce!15885
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
Fixed doc for create MR from email
See merge request gitlab-org/gitlab-ce!15849
|
| | |/
| |
| |
| |
| | |
* fixed anchor for create MR from email
* added a screenshot for this feature
|
| |\ \
| | |
| | |
| | |
| | | |
Clarifies documentation for user, group & project transfers
See merge request gitlab-org/gitlab-ce!15896
|
| | |/ |
|
| |/ |
|
| |\
| |
| |
| |
| |
| |
| | |
Use message body for merge request description
Closes #40968
See merge request gitlab-org/gitlab-ce!15839
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When a merge request is created from email, use message body
as merge request description. If message body is empty then
merge request description is still created from the source
branch commit (if there is only single commit in the merge
request).
If message body is empty and there are multiple commits in
the source branch, then merge request description is left empty.
Closes #40968
|
| | | |
|
| |/ |
|
| |\
| |
| |
| |
| |
| |
| | |
'master'
Add docs explaining why you get signed out with "Remember me" checked
See merge request gitlab-org/gitlab-ce!15756
|
| | |
| |
| |
| | |
See https://gitlab.slack.com/archives/C101F3796/p1512486640000434
|
| |\ \
| |/
|/|
| |
| |
| |
| |
| |
| | |
'master'
Dependency validator
Closes #34834
See merge request gitlab-org/gitlab-ce!14009
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
| |\
| |
| |
| |
| |
| |
| | |
Docs: Update permissions
Closes #40143
See merge request gitlab-org/gitlab-ce!15730
|
| | |
| |
| |
| |
| |
| |
| |
| | |
- Assign issues and MRs
- Label issues and MRs
- Reorder a couple of items in the table to go from unchecked to checked
- Add/remove spaces so that the dividers stay in the same column in the
file
|
| |/
|
|
|
|
|
|
|
|
|
| |
* new merge request can be created by sending an email to the specific
email address (similar to creating issues by email)
* for the first iteration, source branch must be specified in the mail
subject, other merge request parameters can not be set yet
* user should enable "Receive notifications about your own activity" in
user settings to receive a notification about created merge request
Part of #32878
|
| |\
| |
| |
| |
| | |
Add version that the mermaid support was introduced
See merge request gitlab-org/gitlab-ce!15688
|
| | | |
|
| |/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The st_commits and st_diffs columns on merge_request_diffs historically held the
YAML-serialised data for a merge request diff, in a variety of formats.
Since 9.5, these have been migrated in the background to two new tables:
merge_request_diff_commits and merge_request_diff_files. That has the advantage
that we can actually query the data (for instance, to find out how many commits
we've stored), and that it can't be in a variety of formats, but must match the
new schema.
This is the final step of that journey, where we drop those columns and remove
all references to them. This is a breaking change to the importer, because we
can no longer import diffs created in the old format, and we cannot guarantee
the export will be in the new format unless it was generated after this commit.
|
| |\
| |
| |
| |
| | |
Add in the Oxford comma
See merge request gitlab-org/gitlab-ce!15602
|
| | | |
|
