Prepare for liftoff.
Thank you for taking the time to contribute to Houston 👍
Houston would be but a glimmering dream if it were not for the astounding contributions made by third-party developers. To keep contribution as easy as possible, and to keep Houston working as it should, we have put together a comprehensive document of things you should know when contributing to Houston.
Before we get started, please read the elementary code of conduct.
Unsure what needs to be done on Houston? Try looking at some of the issues and submitting a pull request.
If you find an issue or bug with Houston or any of it's appHooks, please submit an issue on GitHub. To help clear confusion and increase productivity, here are some general rules to follow when submitting an issue.
- Use a clear and descriptive title that identifies the problem.
- Include steps to reproduce the issue so developers can test solutions. Even the simplest step is sometimes the cause.
- Include details about your application. This helps developers identify if the issue is only for your application, or for others. This may include links to GitHub repositories or issues.
- If the problem wasn't triggered describe what you were doing before the problem occurred.
- Explain what you expected to happen. Even if it's super obvious.
Pull requests are the best way to see an issue fixed or a feature you want added to Houston. To keep the code clean, and friendly for everyone we have setup some rules you should follow before submitting, all of which are avalible on our wiki page.