![]() ![]() What about the command line versus graphical tools?.In the long term, I also hope to organize the raw thoughts into a decision matrix to highlight which workflow I typically go to when given some set of variables (number of collaborators, type of project, whether it accepts community PRs, team culture, team familiarity with git, etc.).įor most of these topics, the short answer will be "it depends." Expect a discussion of whens, whys, and tradeoffs. I'll be filling these out as soon as time allows, but I wanted to establish a roadmap. Before continuing, please take a look at my thoughts on an effective git learning path. Given that experience, before discussing concrete workflows I feel that it's important to establish that same shared context. When we do have continued discussions, it's much easier because we have a shared context. Sometimes, after covering these concepts, people come to their own solution or answer their own question. When I help someone through an "interesting" situation with git, there are a few concepts that very frequently come up. Through it all, it bears repeating that "it depends." Please take all of this not as a "do or do not" prescriptive screed, but as a guide for evaluating what works best for you and for your teams. Issues will be enabled, so that can be an effective way for anyone to ask questions or bring up additional discussion points. I'll also start out by redirecting you to the resources which I commonly recommend. To mitigate these hesitations, I'm going to attempt to frame my thoughts here as if they were one of those discussions with my team. As to the latter, I have no desire to take the work that others have put in and pretend that it's my own. As to the former, anyone on my teams knows that I'm always happy to pay it forward and share my git experience, but again, it's usually more effective if it's hands-on or a collaborative discussion. One primary reason is that "it depends." Given the nature of the project, the team culture, non-functional requirements like audits and compliance, and a general feeling that there are (over) 9000 ways to do anything with git, a discussion is typically the most effective way forward.Īnother is that over the past eight years, I've come to my understanding of git through hands-on experience combined with leveraging what others already shared. Historically, I have hesitated to do this. People that I work with will frequently suggest to me that I write something about my git workflow(s). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |