Spaces:
Running
Running
| How to contribute to nfl_data_py | |
| Did you find a bug? | |
| Ensure the bug was not already reported by searching on GitHub under Issues. | |
| If you're unable to find an open issue addressing the problem, open a new one. Be sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring. | |
| Did you write a patch that fixes a bug? | |
| Open a new GitHub pull request with the patch. | |
| Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable. | |
| Before submitting, please read the Contributing to Ruby on Rails guide to know more about coding conventions and benchmarks. | |
| Do you intend to add a new feature or change an existing one? | |
| Contact cooper.dff11@gmail.com or @Cooper_DFF on Twitter to discuss. | |
| Do not open an issue on GitHub until you have collected positive feedback about the change. GitHub issues are primarily intended for bug reports and fixes. | |
| Do you have questions about the source code? | |
| Direct any questions to cooper.dff11@gmail.com or @Cooper_DFF on Twitter to discuss. | |
| Do you want to contribute to the nfl_data_py documentation? | |
| Contact cooper.dff11@gmail.com or @Cooper_DFF on Twitter to discuss. | |
| nfl_data_py is a volunteer effort. We encourage you to pitch in and join the team! | |