Terian Koscik

I found some interesting historical information in the original PR for adding the customizable repo prefix field: https://github.com/education/classroom/pull/728 It looks like repo prefixes used to be generated directly from assignment...

Would it make sense to communicate to a user that an assignment title they are providing will lead to a repo prefix with stripped characters, without specifically letting them change...

Should we run a migration/transition to clean up existing user/classroom associations that should have been removed already?

I don't know of a cleaner way than iterating through every user (or organization, whichever has fewer records), I would just make sure to use as few github.com API requests...

I'm not yet certain if this was a case of imports failing or not starting at all. We can add more metrics for API requests that explicitly fail (including browser...

Talked with @JessRudder today about possible ways to prevent problems like this from coming up again: - Automated frontend tests for different browsers (i.e. selenium) - Tracking javascript errors (sentry)...

Making a note here that moving to a GitHub App would also allow us to use an installation token for rate limiting rather than our current strategy of picking a...

Next steps for migrating to a github app: - researching github apps and their tokens - what can they access, maybe even private repos owned by users? - how long...

I did some preliminary research on how we might migrate to a GitHub App. Some notes: - We would need to continue using OAuth to handle user login - The...

Couple more notes: - We can request a user's org memberships through the github.com API and link directly to the installation page for an org through the url `https://github.com/apps/[app name]/installations/new/permissions?target_id=[org...