-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
Discord updates #658
Discord updates #658
Conversation
This page biases towards supervisors reading it, which is fine, however may make it harder to interpret for competitors. This change calls out upfront what a competitor should do to get access in order to avoid confusion.
The last sentence on Line 50 doesn't quite read right, think there needs to be an are in there |
Nice! e55c474 Meta: not sure if you're aware, but it's possible to comment on files in the diff as well as lines. Doing that means we get an inline conversation thread which can be resolved in the usual way, albeit at the top of the file rather than on a line of the file. It's handy for things like this which are outside the diff. |
Wasn't aware of that no, Still learning my way around GitHub. At some point I should probably clone some of the SR repos if only to be better able to review PRs |
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.
Everything looks good to me now.
Suggest review by commit.