Well-formed commit messages?

[hawkrives]

Do we need/want some sort of commit message requirement?

If not:

• how do we make sure to check all submitted assignments?
• What if they complete several in one push?
• How do they tell us that they re-submitted an assignment?

[OmarShehata]

What if we had them under the assignment number in the commit message? So a commit of hw2 would just run all homework 2 checks. So even if you're only submitting part of it, it'll tell you, you're missing X,Y and Z, but W is complete, so you are 30% complete.

And they can resubmit as much as they want by just committing with that message.

[hawkrives]

So you just always include a hw# / lab# in your commit message, and it will run a check?

[hawkrives]

In the case of multiple commits being pushed, we should probably filter out any duplicates so that we only check the latest versions of each assignment

[OmarShehata]

That sounds like the most straightforward to me. So the student knows what checks will run, and she knows it's all good when the commit message comes back as "100% complete!".

[hawkrives]

Something else to keep in mind: we're going to need some way of automatically updating the specs / checkers on the gitlab machine

[OmarShehata]

More webhooks! We can have it automatically pull down and run whatever script whenever someone pushes to the Referee repo. That's what I did for the HiPerCiC documentation, where it pulls and runs a script to convert the reStructured markup into html.

[hawkrives]

Great!