|
|
|
|
|
|
|
Re: git clone without rebase config [message #1830755 is a reply to message #1830739] |
Mon, 03 August 2020 09:28 |
Ed Merks Messages: 33148 Registered: July 2009 |
Senior Member |
|
|
I'm not sure exactly how to interpret the documentation. From the documentation, I get the sense that the value of the rebase property can be "true", "preserve", "interactive", and "merges ", but playing with the EGit settings, I only see it setting the rebase property to "true", "preserve", "interactive", and "false", and once set, there is no way to remove it entirely. I'd want to ask the EGit experts for clarification on this.
But I can imagine defining an EEnum in the Git.core model with similar (the same) choices as EGit has for this, though as you suggest with an additional option (enumerator) for removing the property entirely (or not setting it at all). This could then be used as the type a rebase attribute on the GitCloneTask for directing the behavior and could then be used in GitCloneTaskImpl to change the current hard coded behavior.
You could use the following to set up a development environment to contribute such a feature:
https://www.eclipse.org/setups/installer/?url=http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/configurations/OomphConfiguration.setup&show=true
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04075 seconds