updated fork feature to use gitlab-shell for v5 of gitlab
Created by: amacarthur
Replaces pull request https://github.com/gitlabhq/gitlabhq/pull/3382
Dependent upon gitlab-shell pull request: https://github.com/gitlabhq/gitlab-shell/pull/45
This will provide a button on the project page which will create a fork of a project into their own namespace. The fork from/to relationship is recorded in anticipation of gitlab handling cross-repo pull requests.
Created by: amacarthur
Is there anyway to retry the build? The failure is in an area entirely unrelated to my changeset, and from what I've seen, capybara is prone to intermittent falure.
1) On a merge request diff with muliple note forms posting a note should be added as discussion Failure/Error: find('a[data-line-code="342e16cbbd482ac2047dc679b2749d248cc1428f_18_17"]').click Capybara::Ambiguous: Ambiguous match, found 2 elements matching css "a[data-line-code=\"342e16cbbd482ac2047dc679b2749d248cc1428f_18_17\"]" # ./spec/features/notes_on_merge_requests_spec.rb:128:in `block (3 levels) in <top (required)>'
By Administrator on 2013-04-18T19:36:15 (imported from GitLab project)
Created by: fbender
So if I understand correctly, you cannot merge (PR/MR) forks back into any branch of the original repo. However, I think it is vital for this feature to actually allow to send your work in the forked repo back to the original one. Is this being worked on somewhere else?
By Administrator on 2013-04-28T22:17:20 (imported from GitLab project)
Created by: amacarthur
Travis build failed only when attempting to run with Ruby 2.0.0. The failure is due to a known Ruby 2.0.0 issue. See https://github.com/rails/rails/issues/9417#issuecomment-14054219
By Administrator on 2013-05-02T21:13:24 (imported from GitLab project)
Created by: dzaporozhets
@amacarthur since
private method `initialize_dup' called for #<Project
for ruby 2.0 we should find a better solution. We already use 3.2.13 and I'm not sure its rails related (even if true they are not going to provide a release in closest month I guess) so we should fix it.
By Administrator on 2013-05-03T07:14:01 (imported from GitLab project)
Created by: amacarthur
Fix for failure using ruby 2.0:
https://github.com/gitlabhq/gitlabhq/pull/3829
By Administrator on 2013-05-03T16:16:26 (imported from GitLab project)
Created by: junxy
Suggest fork feature add configurable options, and default project features settings, Just like: gitlab.yml
## Default project features settings default_projects_features: issues: true merge_requests: true wiki: true wall: false snippets: false fork: false ##here
Thanks!
By Administrator on 2013-05-30T07:11:20 (imported from GitLab project)