+1 Prescriptive workflow approach is the best. I am not competent with git, and this is the approach I have taken. I keep note of frequently used commands and s

+1 Prescriptive workflow approach is the best. I am not competent with git, and this is the approach I have taken. I keep note of frequently used commands and solution to frequently encountered problems. I have gone through multiple tutorials from AWS CodeCommit, GitHub, etc but the most helpful has been describing the problem to someone more knowledgeable and have them guide me. Someday git will make sense to me but it is not going to be today or anytime soon. Telling someone to take a course or go through a tutorial or read a book doesn't help that much, actually it is more discouraging and give impressions of an unhelpful colleague, as a new guy. Depending on GUI or Built-in IDE git features are not the solution, getting to know simple raw native git commands for tasks at hand or problem being faced is the best approach, imo.