Commits Job, User view

[pconrad]

As an instructor or admin, I can run a job that populates a table of commits.

• [ ] There is a job button to run "refresh commits"
• [ ] The purge github data purges the commits data for the course.
• [ ] The "refresh commits" job get all commits from all repos where the user matches a user currently in the github linker user table, and populates the commits table.
• [ ] On the RosterStudent show page, there is a link to "Commits" for this user.
• [ ] There is a "commits" for this user page that shows a list of all commits.
• [ ] For the MVP, it should simply be sortable columns. But among the most important, and probably, left most: date/time of commit, repo.

LATER: Filter on that page by repo, start/end date/time.

Commits table:

• id, course_id, user_id, data from the commit... (tba)

NEXT STORY:

I can see all of the commits for a given team, aggreated together in some coherent view:

From Team page, a link to a "Team Commits"

• MVP: same view as the User Commits page, but there is now a column for user, and the data is all commits for all members of the team?

[ProbablyFaiz]

For future reference, here's a GraphQL query I've assembled mostly from here that does most of this (pagination handling aside):

{
  organization(login: "org-name") {
    name
    repositories(first: 49) {
      totalCount
      nodes {
        refs(refPrefix: "refs/heads/", orderBy: {direction: DESC, field: TAG_COMMIT_DATE}, first: 100) {
          edges {
            node {
              ... on Ref {
                name
                target {
                  ... on Commit {
                    history(first: 100) {
                      edges {
                        node {
                          ... on Commit {
                            message
                            committedDate
                            author {
                              name
}                          }                        }                      }                    }                  }                }              }            }          }        }      }    }  }}

Note: the constants 49, 100, and 100 are deliberate. Raising these will cause GitHub to reject the query as it could exceed their limit of a maximum of 500,000 nodes in one request.