Branch for each of the different assignment tasks,
Merge back into final report
We haven’t actually done this yet, but this is how I imagine students working on a simple website, adding content first, then creating layout elements, and styling it all in the end.
No real workflow here yet. Playing around to understand the basics and get a feeling of what it can contribute to classroom activities in a non-programmers department.
This is so cool!
You can delete the branch, or, as you get more comfortable, cherry pick the commits you want to move:
There are more advanced workflows for this, including reset hard and rebase. There’s documentation on those commands if you’d like to find out more:
@MrODonnell the of branches is that, 99% of the time, we’re on a branch, so we’re almost always using them.
I like using that second for your code sample project.
@OmalPerera here’s a diagram of a real-world workflow…might you want to include a development branch in addition to features?
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.