Git Clone Task - redirect to private fork [message #1692707] |
Fri, 17 April 2015 08:12  |
Eclipse User |
|
|
|
Assume that I want to contribute to a GitHub project for which I have no write access. Typically, I will fork the repository, make the change, push it to my fork and create a pull request. Right?
If the project provides an Oomph setup, it will involve a GitCloneTask pointing to the original repository. Ideally, I want to reuse the original setup for my own fork without having to modify it.
I tried creating a redirect task (redirecting the original URL - which I have to find out beforehand - to the fork URL) in the User model prior to installing the project. This seemed to work, but I was wondering if this is the recommended way for dealing the the above scenario. Possibly, there are better solutions or built in features?
Alex
|
|
|
Re: Git Clone Task - redirect to private fork [message #1692753 is a reply to message #1692707] |
Fri, 17 April 2015 10:35   |
Eclipse User |
|
|
|
Alex,
Most of the setups I've authored, a list of clone choices are offered,
i.e., https, git, ssh versions, so in that field one could enter the
clone of a fork...
On 17.04.2015 14:12, Alexander Nittka wrote:
> Assume that I want to contribute to a GitHub project for which I have no
> write access. Typically, I will fork the repository, make the change,
> push it to my fork and create a pull request. Right?
>
> If the project provides an Oomph setup, it will involve a GitCloneTask
> pointing to the original repository. Ideally, I want to reuse the
> original setup for my own fork without having to modify it.
>
> I tried creating a redirect task (redirecting the original URL - which I
> have to find out beforehand - to the fork URL) in the User model prior
> to installing the project. This seemed to work, but I was wondering if
> this is the recommended way for dealing the the above scenario.
> Possibly, there are better solutions or built in features?
>
> Alex
|
|
|
|
Powered by
FUDForum. Page generated in 0.04719 seconds