Initially we planned to do this before the hackathon:
Change can_attend_next before every hackathon (need a better definition of the trigger for this, but the verification should be based on rules
But after some assessment I'm proposing with this MR to do it at every grading. This way, at whatever point in time the spec has X units, if the student has passed all with a specific grading, he'll automatically be marked as eligible for the next hackathon. This will help us keep all info updated instead of waiting until the last date and compute everything.
Initially we planned to do this before the hackathon:
But after some assessment I'm proposing with this MR to do it at every grading. This way, at whatever point in time the spec has X units, if the student has passed all with a specific grading, he'll automatically be marked as eligible for the next hackathon. This will help us keep all info updated instead of waiting until the last date and compute everything.
Closes #171