Thank you for helping out with the Open Source Clubs's Resources!
Following these guidelines helps us keep good project workflow. We appreciate you working with us on it.
Please read our CODE_OF_CONDUCT.md to understand our community expectations. Check out our Discord for any additional questions or just to hangout!
Please check the Issues page for current tasks. If you see something that you would like to help with, ask about helping in a comment and we'll assign it too you. If you're just starting out, checkout our beginner friendly issues for ways to help.
Check to see if the feature is already an [Issue][Issue] . If it's not, describe the feature and why it would be beneficial. Create an Issue with this description and add a feature enhancement label. We will do our best to respond quickly to it.
- Create a fork or branch of dev to tackle a specific issue
- Name it after the issue or feature you are working on
- Follow the style guidelines below
- This helps with debugging and working on the project
- Make small incremental commits
- It's easier to find issues when only a small amount of code is changed
- Run and pass tests
- Some of our larger projects use Travis for Continuous Integration (CI).
- Make a pull request
- The request will be reviewed
- If there is not a response after a few days, try contacting the project lead
- Any needed changes will be noted
- The request will be reviewed
- The changes will be added to the project
- Yay! Thank you so much for helping out
Use our .editorconfig to help automatically format your code.
For a more descriptive list, check out our club's markdown style guidelines.