Line changes are a horrible way to judge amount of work.

A slightly more accurate method would be to use World Syntax Tree to find the graph edit distance between commit trees. (Need to add that feature to WST)

All of the student repos can be imported into a WST db for analysis. Each commit can form a new point in the comparison, allowing an estimate of work to be generated for each contributor & commit.

On PR merge, execute scripts/org-membership.py

Proposed enhancements to scripts/org-membership.py:

• On duplicate detection: Assign duplicate tag to PR.
• On students not being invited: invite to team, add 'invited' label to relevant PR.

Modifications to students.yml will not be committed to main, but submitted via PR. If the PR already exists, then use that one.

...

Github Action: Linked Issue checker

Aims to reduce the number of dangling commits by tracking them and notifying students.
This check will run for each commit pushed to main, facilitated by a hook / GitHub action.

Any commits to be counted toward an iteration

• in student repos
• have a linked commmit

Students can link these commits in two ways:

• by including the issue number in the commit message on creation
• by linking via commit hash in a comment in the issue
• revising a commit message to link it to an issue

It should be verified that the commit is linked to a valid issue

To communicate commits that are not properly linked, they could be linked to a "dangling commits issue" or included in a discussion post.

Issues that should be linked should be in

Validates that git commits are linked with an issue

Runs on push hook

https://www.youtube.com/watch?v=dQw4w9WgXcQ