|
|
| Re: Predefining the Git clone location rule and Root Git-container folder [message #1819219 is a reply to message #1819216] |
Fri, 10 January 2020 07:28   |
|
> I'm hesitant to answer this because I expect you'll use that knowledge to take this choice away from the user and impose on them your personal choice.
Looks like you hesitant to impose your personal preference. ;-)
> In general look closely at your user.setup (Navigate -> Open Setup -> User)
Thanks, I try to find this. Multiple clones of the same repo to work on different branches are nothing I have ever heard anyone suggest from the Git community. Such a setup still feels like a memory from the good old cvs / svs days to me.
If you have a pointer to such a recommendation coming from a Git related source (e.g., Github, Bitbucket) etc., please let me know.
For reference: I migrated multiple clients from cvs/svn to Git, contributed patches to the Git command line and EGit tooling, wrote a book on Git command line tools and worked for the Github company in the past.
If multiple parallel checkouts are needed: the Git command line supports multiple working trees for the same repo to cover you scenario. See https://dev.to/oliverjumpertz/using-multiple-working-trees-in-git-122d
|
|
|
|
| Re: Predefining the Git clone location rule and Root Git-container folder [message #1819223 is a reply to message #1819222] |
Fri, 10 January 2020 08:36 |
|
> Perhaps each of us (me included) is deaf to information that does not conform to our expectations or our mental model of the world as it is or should be...
I hope I never questions your personal way of working. If you like cloning multiple times to support certain scenarios that is fine to me. I never needed that (Git branch switching works fine for me) and the original Oomph tooling did (before you added it) not support that way of working which is AFAIK the norm if standard Git tooling is used.
In general I dislike if a tool force me to use a different approach that the tooling which is used under the hood. If I clone via Git command line or EGit the resulting directory does not include the branch name, hence any tooling which wraps the Git clone operation should IMHO offer the same approach.
Saying that this requirement is similar to "fall on deaf ears" show a strong personal preferencem for the personal way of working. Supporting and accepting different way of working than the personal one is important IMHO for tooling be get accepted.
So in my personal summary: It is IMHO great that Oomph now allows to clone similar to the standard Git and EGit tooling. Not to great is that the option to pre-configure this is not documented.
|
|
|
|
|
| Re: Predefining the Git clone location rule and Root Git-container folder [message #1819230 is a reply to message #1819229] |
Fri, 10 January 2020 09:28 |
|
> As I mentioned in this Bugzilla in response to your request, there is a choice for the layout style
Yes, thank you for that. That is excactly what I meant with: "It is IMHO great that Oomph now allows to clone similar to the standard Git and EGit tooling" statement.
> Then I would decide if I needed/wanted those in the maintenance stream as well, I would pull in that IDE and cherry pick what I wanted.
Your process to use a server to bring branches together sounds not very gitty to me . ;-) Also this way of working would not allow to use the popular Gitflow branching model (https://blog.axosoft.com/gitflow/)
But the power of Git is that its supports different ways of working and if this process works fine for you, than that is good and OK. Let me repeat: I never intended to question your way of working.
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04099 seconds
] 
Search
Help
Register
Login
Home
