Hi @eliasnogueira what’s going on in your assignment workflow? Do assignments2 and assignments3 merge back into the master branch at some point?
Honestly, I am working through this to prep using this for real. So, it has not really happened yet. I would have them merge back after they get a feature working.
I’m not teaching at this moment. I start in a few weeks and i have to convince the head teachers to star to use git hub
In the mean time I learning how to implement this in a class. So, I invented a thing to do this exercise:
This is an individual assignment.
Assignment consists to implement a console application in C#
Starter code will be provided by teacher (first commit)
Student can develop features with branchs (work for mandatory work) and improves for introducing additional features and merge to master to present the work.
Because my classroom work has us using the remote repo and I couldn’t get the visualization tool to hook up to that, my screen shot “isn’t much”. But here it is:
I did find out about request-pull, that’s an interesting command I will add to my repertoire and teaching information.
Basically, our flow is:
- checkout branch
- make changes and commit
- push to github
- pull-request and merge on github
- pull to master
- merge master to branch
repeat until project is done
From a given starting point, students develop serveral distinct features, which will be merged at the end.