Skip to content

Latest commit

 

History

History
31 lines (16 loc) · 1.39 KB

CONTRIBUTING.md

File metadata and controls

31 lines (16 loc) · 1.39 KB

How to contribute to PushIn.js

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.

Please use the Bug Report issue template to help create a detailed report of the issue.

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.

Do you intend to add a new feature or change an existing one?

If there is no open issue for this change, please open a new one using the Feature Request issue template in order to thoroughly document the goal of this feature change. If you have already made this change, please open a pull request and include a link to the corresponding issue for further explanation of what has been done.

Development setup

For more information on how to set up your development environment, please see DEVELOPERS.md.

More questions?

Ask any questions about how to use or contribute to PushIn.js in the Discussions section of the GitHub repository.

Thanks! ❤️ ❤️ ❤️

PushIn.js Team