-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update 2i2c access management #326
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ateucher this is great. I fully understood the flows. Beyond minor text suggestions, I left one comment for you and Julie to consider re: harmonize Team & repo names for Champions.
Co-authored-by: Stefanie Butland <[email protected]>
Thanks so much @stefaniebutland for the review! |
I've created an issue from the outstanding comment from @stefaniebutland. @jules32 do you want to review this as well, or if Stef is happy with it can she approve and merge? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Andy! This looks great, I have had a quick review and made a few suggestions; please feel free to merge afterwards! We can continue to update it as we use it if we see places to clarify/add. THANK YOU!
Co-authored-by: Julia Stewart Lowndes <[email protected]>
I think this is ready for a review now. There is still a bit of an awkward step between the google sheet of form responses and adding to the team, as the form doesn't record the exact name of the team to which they should be added (if it is a workshop or cohort). So we must use context (date form filled out and access type specified) to infer it. It's probably fine, but could possible be addressed on the form side...