I have been Watching YouTube tutorials in order to expand my knowledge in git but there are now some questions that this has raised so I was hoping someone here could educate me on some best practices or philosophies I should consider.
The main point is around rebase - I see great value in this but the whole philosophy was around bringing committed code into your feature branch. I will regularly create feature branches for each new enhancement or fix. The problem rears its head when testing is delayed and the first feature (feature-branch-1) is still not approved for production and sits as a branch awaiting merge. Now, in my feature-branch-4 I am working In a similar area and really need to consider changes from feature-branch-1 and I usually just copy some of those changes over. Now this is not very efficient and I thought rebase would work great BUT that code is not approved and may actually change. I really just don't know what's the most efficient way to manage situations like this without stopping development and waiting for testers to approve code but this approach results in 1-2 days of waste where I just twiddle my fingers waiting... Any advice or personal experience would be welcome. -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/fa00ea44-d8ea-417b-8cdb-441f14cf99aan%40googlegroups.com.
