GitLab FOSS merge requestshttps://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests2019-09-20T02:31:41Zhttps://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/1Fix Links To Gitlab Cloud2019-09-20T02:31:41Zusername-removed-2900Fix Links To Gitlab CloudMissing slash breaks links to GitLab.comMissing slash breaks links to GitLab.comhttps://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/5Allow PHP syntax highlighting without open tag2014-02-11T19:55:51Zusername-removed-15584Allow PHP syntax highlighting without open tagThe PHP lexer for Pygments normally requires PHP code to start with `<?php`. It has, however, an option to allow this open tag to be omitted. This option (`startinline`) is only recognized by the PHP lexer and has no drawbacks because mi...The PHP lexer for Pygments normally requires PHP code to start with `<?php`. It has, however, an option to allow this open tag to be omitted. This option (`startinline`) is only recognized by the PHP lexer and has no drawbacks because mixing HTML and PHP is deprecated anyway and for cases where you really want to have it, there is an html+php lexer. Therefore it has been [determined](https://github.com/imathis/octopress/pull/1141) that this option can always be enabled.
![Before](http://i.imgur.com/rI8D6Al.png "Before")
![After](http://i.imgur.com/yw4i58A.png "After")
https://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/7Wiki With Images Downloads & Folders2016-12-15T15:09:02Zusername-removed-15782Wiki With Images Downloads & FoldersA draft implementation to support folder hierarchies and serving of raw files (images, PDFs, anything) in the Gollum wiki.
I'd appreciate your feedback in order to try and get this closer to a mergeable solution, fixing http://feedbac...A draft implementation to support folder hierarchies and serving of raw files (images, PDFs, anything) in the Gollum wiki.
I'd appreciate your feedback in order to try and get this closer to a mergeable solution, fixing http://feedback.gitlab.com/forums/176466-general/suggestions/3935963-allow-wiki-pages-to-show-images and allowing the wiki to be a bit more useful.https://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/10Spelling error in the upgrader guide.2014-02-10T16:49:11Zusername-removed-16616Spelling error in the upgrader guide.Small issue, but it was kind of annoying me :) Small issue, but it was kind of annoying me :) https://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/13Add a comment to gitlab.yml.example for cusom installing2017-08-15T12:57:51Zusername-removed-16837Add a comment to gitlab.yml.example for cusom installingI've setup production server on my VM following installation.
https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/install/installation.md
When I tried to use "relative_url_root", I faced some error and needed to search informatio...I've setup production server on my VM following installation.
https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/install/installation.md
When I tried to use "relative_url_root", I faced some error and needed to search information about it.
So I added a maybe helpful comment to gitlab.yml.example to avoid above error.
Finally, thank you for hosting such a great project!https://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/17Fix Long Names Admin Dashboard2020-03-16T23:49:37Zusername-removed-18103amwiddersheim@gmail.comFix Long Names Admin DashboardWhen there is a long project, group or user name and you are in the admin dashboard the long strings can mess up the formating. This commit truncates those names to a reasonable size similar to how the project names on the user dashboard...When there is a long project, group or user name and you are in the admin dashboard the long strings can mess up the formating. This commit truncates those names to a reasonable size similar to how the project names on the user dashboard get truncated.https://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/22Fixes 67 Relative Markdown Link Relative Root2014-03-08T02:11:40Zusername-removed-17384Fixes 67 Relative Markdown Link Relative RootFixes relative markdown link under RAILS_RELATIVE_URL_ROOT
Under RAILS_RELATIVE_URL_ROOT, relative links are broken since they omits the relative root. I.E.
```markdown
[some link](my_resource.md)
```
would points to `...Fixes relative markdown link under RAILS_RELATIVE_URL_ROOT
Under RAILS_RELATIVE_URL_ROOT, relative links are broken since they omits the relative root. I.E.
```markdown
[some link](my_resource.md)
```
would points to `http(s)+://hostname/namespace/project/my_resource.md` instead of `http(s)+://hostname/relative_root/namespace/project/my_resource.md`
The proposed patch fixes this issue, and works in the case where `Gitlab.config.gitlab.relative_url_root` is either :
* '/foo'
* 'foo'
* ''
* nil
https://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/23Fixes 67 Relative Markdown Link Relative Root2014-06-04T13:01:05Zusername-removed-17384Fixes 67 Relative Markdown Link Relative RootThis small patch fixes issue #67, and should work in case Gitlab.config.gitlab.relative_url_root is
* '/foo'
* 'foo'
* ''
* nil
This small patch fixes issue #67, and should work in case Gitlab.config.gitlab.relative_url_root is
* '/foo'
* 'foo'
* ''
* nil
Marin JankovskiMarin Jankovskihttps://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/25Add Alternate Ssh Host Option2016-11-09T14:24:19Zusername-removed-18231Add Alternate Ssh Host OptionThis adds a config option to allow gitlab to populate a different url for `git@domain.com:namespace/repo.git` for people that split their SSH connections onto different VLAN or Listening IP than their GitLab web install or have strict fi...This adds a config option to allow gitlab to populate a different url for `git@domain.com:namespace/repo.git` for people that split their SSH connections onto different VLAN or Listening IP than their GitLab web install or have strict filewall rules etc.https://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/27Hides branch selector drop down box2020-03-16T23:46:59Zusername-removed-18832Hides branch selector drop down boxShows branch selection drop down only in commits sub tab.
In the current implementation it only has a functionality within the Commtis view.
In other tabs it will confuse due to the semantic suggests that you might switch the view fo...Shows branch selection drop down only in commits sub tab.
In the current implementation it only has a functionality within the Commtis view.
In other tabs it will confuse due to the semantic suggests that you might switch the view for tags/stats onto a branch or select the root for a comparisation operation for the selected branch...which isn't the case.https://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/29Fix Spinach Test2014-03-04T16:36:09Zusername-removed-15699Fix Spinach TestA test was broken by f0750b9166dd729383c4b3f865c80bb024d03798. This fixes that.A test was broken by f0750b9166dd729383c4b3f865c80bb024d03798. This fixes that.https://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/31Merge Request links incorrect after having deleted projects2014-04-13T21:16:57Zusername-removed-19157Merge Request links incorrect after having deleted projectsWhen linking to the specific lines in the diff, the project number is incorrect for the merge request which results in a 404 page rather than linking to the diff.When linking to the specific lines in the diff, the project number is incorrect for the merge request which results in a 404 page rather than linking to the diff.https://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/32Do not show 404 if repository is empty2020-03-16T23:49:56Zusername-removed-18832Do not show 404 if repository is emptyIf the repository does not contain any files GitLab will show a 404 error for the files view ( https://gitlab.com/gitlab-org/gitlab-ce )
New behavior will show an empty file view and do not show the download archive due to download zi...If the repository does not contain any files GitLab will show a 404 error for the files view ( https://gitlab.com/gitlab-org/gitlab-ce )
New behavior will show an empty file view and do not show the download archive due to download zip would be 0 Bytes.https://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/33WIP Dockerfile2015-02-11T18:58:43ZSid SijbrandijWIP Dockerfilehttps://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/34Simple one line ruby script upgrade command2014-04-04T08:17:24Zusername-removed-2435Simple one line ruby script upgrade commandAdded simple one line ruby script upgrade command.Added simple one line ruby script upgrade command.https://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/39Added description parameter support to Create and Update MR API endpoints2014-03-16T07:43:01Zusername-removed-20493Added description parameter support to Create and Update MR API endpointsSometime in the past the GitLab UI added a Description field to the Merge Request form, unfortunately the description was never added to the Create and Update MR API endpoints. This request will add the description parameter to both the ...Sometime in the past the GitLab UI added a Description field to the Merge Request form, unfortunately the description was never added to the Create and Update MR API endpoints. This request will add the description parameter to both the Create and Update MR API endpoints in lib/api/merge_request.rb
This was reported by me in [Issue 110](https://gitlab.com/gitlab-org/gitlab-ce/issues/110).https://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/43Fixing package name2016-11-28T16:53:03Zusername-removed-21559Fixing package nameI noticed while trying to install GitLab (as well as GitLab CI) that they refer to libxslt-dev, but I believe it should be libxslt1-dev.I noticed while trying to install GitLab (as well as GitLab CI) that they refer to libxslt-dev, but I believe it should be libxslt1-dev.https://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/44update changelog2014-03-15T17:53:21Zusername-removed-15305update changelogUpdate the changelog to add the 6.6.X entriesUpdate the changelog to add the 6.6.X entrieshttps://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/46Update/Deploy.Sh2015-01-05T15:57:17Zusername-removed-15305Update/Deploy.ShUpdate deploy.sh
add variable for home directory
use `/bin/bash` for the scriptUpdate deploy.sh
add variable for home directory
use `/bin/bash` for the scripthttps://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/47Merge Request Versions (1st take)2020-03-16T23:24:28Zusername-removed-20168Merge Request Versions (1st take)This adds patch versioning support for merge requests by generating a new `MergeRequestDiff` entity each time a `MergeRequest#target_branch` is updated (via `git-push`).
This feature, aims to greatly improve code review by allowing th...This adds patch versioning support for merge requests by generating a new `MergeRequestDiff` entity each time a `MergeRequest#target_branch` is updated (via `git-push`).
This feature, aims to greatly improve code review by allowing the reviewers to see the progress of the patch across updates.
A reviewer could approve most changes in a patch version and then just do a `interdiff` with future versions instead of having to review the entire patch again.
This workflow is inspired by _ReviewCode_ and derived from my comment on: http://feedback.gitlab.com/forums/176466-general/suggestions/3896541-preserve-conversations-on-merge-requests-after-com
Currently, only _diffs_ are displayed, not _interdiffs_. But you can manually get an `interdiff` by downloading both _raw diffs_ versions to compare; for example, to compare versions 1 and 2 of a merge request you would do something like this:
```bash
interdiff \
<(curl -s -H 'Cookie: ....' 'http://your.gitlab.installation/<group-name>/<project-name>/merge_requests/<mr-iid>.diff?version=1') \
<(curl -s -H 'Cookie: ....' 'http://your.gitlab.installation/<group-name>/<project-name>/merge_requests/<mr-iid>.diff?version=2')
```
You could also pipe the _interdiff_ through _colordiff_ to get a better output.
I'm currently test driving this feature in my daily workflow and would really like know what you think about it too.