First off, thank you for considering contributing to the Github-Webhook-Resource! This resource is a simple project, but has plenty of room for improvement. Many features of Github's webhook implementation are yet to be built into the Github-Webhook-Resource, and all contributions are welcome.
If you're just looking for quick feedback for an idea or proposal, feel free to open an issue.
Follow the contribution workflow for submitting your changes to the Github-Webhook-Resource codebase.
The Github-Webhook-Resource uses the “fork-and-pull” development model. Follow these steps if you want to merge your changes to the Github-Webhook-Resource:
- Within your fork of the Github-Webhook-Resource, create a branch for your contribution. Use a meaningful name.
- Create your contribution, meeting all contribution quality standards
- Create a pull request against the master branch of the Github-Webhook-Resource repository.
- Add a reviewer to your pull request. Work with your reviewer to address any comments and obtain an approval. To update your pull request amend existing commits whenever applicable and then push the new changes to your pull request branch.
- Once the pull request is approved, one of the maintainers. will merge it.
Your contribution needs to meet the following standards:
- Separate each logical change into its own commit.
- Add a descriptive message for each commit. Follow commit message best practices.
- Document your pull requests. Include the reasoning behind each change, and the testing done.
- Acknowledge the Apache 2.0 license.