obdurodon / dh_course

Digital Humanities course site
GNU General Public License v3.0
20 stars 6 forks source link

Discussion post: Git #422

Closed charlietaylor98 closed 4 years ago

charlietaylor98 commented 4 years ago

Since my first encounter with the command line, using it has become less intimidating. Trying to get a project up and running that involves a lot of moving parts, I can see the importance of different people being able to work separately and smoothly merge their work into one file. I'm still trying to get a grasp on when it's appropriate to do certain things in Git, ie when to stash to the working directory and when to commit, but I'll be able to best learn those things once I get more practical experience. On Github, I'd like to know more about managing branches; since our corpus is pretty large it would benefit us to work from multiple branches to avoid error as best as possible.

djbpitt commented 4 years ago

Branches are common in what is sometimes (vaguely) called the Git workflow (see, for example, https://git-scm.com/book/en/v2/Git-Branching-Branching-Workflows). There are a few different strategies for using branches to manage development, and this is a good topic to discuss in a project meeting.