![]() It’s clean and simple and I like the fast filterable searching, but it’s clearly dated and I can’t even figure out how to export the events to a simple. I am currently using the free QuiteRSS feed reader. Also, sometimes events are missing in general whether I was fetching regularly or not… For example, I can find evidence of a commit on GitHub, but my feed reader never got the event Am I just using a poor reader? Did I just not turn my computer often enough that day/weekend? But no, I seem to have other events before and after it… And now I have no data on those events to compute with or to find dependencies between commit and push timestamps, etc. I don’t know how long the feed is, but it is limited. If I don’t fetch for a day or two, there are definitely events missing. The problem I have with this solution is that you have to keep fetching often (daily at least) to get all events. I am still currently using an RSS/Atom feed reader to read the Dashboard feeds from appropriate organizations, such as: I found the Dashboard, which is filterable by organization, and is where I found the RSS/Atom feeds, but the web Dashboard isn’t searchable and is limited, both in terms of how I can interact with it and in content, I can’t export it, etc. ![]() Then I tried the audit log of an organization, but it doesn’t seem to have all the information… I find plenty of admin events, but nothing by students (probably because they are not admins). Emails were sporadic, unreliable, waste of bandwidth, definitely not a good way to organize data, etc. ![]() I’m embarrassed I even thought that was an acceptable approach for hundreds of repos per semester. just better insight in general into how my students are working with their GitHub reposĪt first I tried getting notification emails filtered into folders… which was admittedly a very horrible idea on my part.daily / periodic queries to get ahead on grading early.fast searching across all events for a particular student, particular repo, particular organization, etc.Ultimately, I’d like to provide these activity graphs to the entire class as feedback and even student/project specific graphs during grading… graphing various metrics like when students (individual and whole class) are starting assignments (repo creation), activity over the week/month (number of commits, activity in general).if they push after assignment is graded, GitHub shows commit timestamp in history (for obvious good reasons), but I still need to know the difference as a teacher who is grading… push time vs commit time for students who forget to submit (push) on time.even with my lame solutions, it has helped me communicate with my students about what they are doing right and wrong, and gives me insight into how they are using it, and provides evidence for grading.So I threw together a tool to query it for any given student repo. GitHub’s documentation claims this data will survive for 90 days after the events in question. Yeah, really.Ĭonveniently, GitHub has an events API that lets you query the push time for every commit. ![]() I had a curious issue where a student had apparently attempted to change the time on their computer, perhaps thinking they could fool GitHub. A tool to print all the "push" times for your students' commits GitHub Classroom
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |