How to contribute to file_tree
Did you find a bug?
Firstly, 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.
A note on PR. When creating PR follow the best practices for Git branching naming convention . More information on it can be found here:
https://codingsight.com/git-branching-naming-convention-best-practices/
Do you intend to add a new feature or change an existing one?
Suggest your change by sending an email ali852609@gmail.com and start writing code.
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?
Ask any question about how to use file_tree by sending an email to ali852609@gmail.com .
Thanks!