-
Notifications
You must be signed in to change notification settings - Fork 57
Conversation
@@ -0,0 +1,170 @@ | |||
# Contributing to Reservations | |||
Thanks so much for helping with the development of Reservations! This guide will cover the process for helping out with the project and should allow you to get started quickly and easily. If you need any help with contributing, please e-mail `stc-reservations{at}yale{dot}edu` to contact the core team. | |||
|
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.
If you want we could also mention that they can @-mention the core team with @YaleSTC/reservations
Would you mind making this fit 80 chars per line? |
Is it standard to have markdown files be 80 characters long? I guess the Atom guide basically does it (with exceptions for links), no reason not to. |
Ok, 80 characters or less it is (more or less, some exceptions made for links and some other formatting). Let me know if I screwed anything up while splitting up lines or if there are any other changes to make, thanks! |
fork as the head fork with your branch as the compare brach. Click "Create | ||
Pull Request" and add a description which references the original issue (e.g. | ||
`Resolves #1234`), describes the changes you made and any new tools or | ||
libraries you added, as well as any breaking changes. |
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.
I think anywhere we have a list of steps (like this section) we should have bullet points
Ok, fixed the last couple of comments. How does it look? |
Resolves #1056
dea58e4
to
d117a4a
Compare
Resolves #1056, please check for typos but also make sure the content is good and makes sense. Thanks!