When working on a branch, I stay off other branches and my main branch as much as possible.If I am really uncertain about an idea/change or about to make a major revamp, I’ll make a branch while working on the idea, once I decide yeah/neah, I merge the branch into main and delete the branch. work on a file or set of files, finish work, merge into main, delete the branch.I do use branches regularly with certain R package projects and when I use them, it is in very specific ways The GitHub features I talked about so far are things that are already part of our workflow (taking notes on what we are doing, saving copies along the way, reviewing work with collaborators, sharing our work) but Git/GitHub allows us to do it more efficiently, better and faster. Normal scientific workflow does not involve branches and IMO most scientists won’t gain much by adding that to their workflow. Even through I work on many Git repositories and develop public R packages, it is rare that I need to use branches. In the lecture, I cautioned against using branches when you are beginning with Git. This video shows a basic workflow using branches.
0 kommentar(er)
