We want to make contributing to this project as easy and transparent as possible.You can help this project by reporting problems, suggestions, locating it or contributing to the code.
Go to our issue and check if your problem / suggestion has already been reported. Otherwise, create a new issue with a descriptive title and detail your suggestion or steps to reproduce the issue. A good bug report should not let others need to chase you for more training. Please try to be as detailed as possible in your report.
This repository has some features in order to facilitate the organization of work.
The branches are distributed in:
-
master - Stable version. Something will only be added to this branch when it is really relevant for the release of a new version.
-
beta - Stable version that contains most of the major features, but is not yet complete.relevant to the launch of a new beta version on release.
-
dev - Unstable version. It is the continuous version of development. All approved and tested modifications will be added to this branch.
-
inbox - Branch for receiving Pulls Requests. All pulls must be directed to this branch, which, if approved, will be merged into the dev.
-
draft - Draft branch, used when testing new features and pulls.
-
news - Branch containing the current functionality under development by the maintainer.
When developing wp3, follow these steps to setup your environment, format your code, and run app and unit tests:
if you want to develop a new feature, use a unit testing framework to create unit tests, run them, and report the results of these tests. i recommend frist create a unit tests test_features.py
into directory tests
.
-
Fork [wifipumpkin3][] on Github.
-
Clone the git repo:
$ git clone https://github.com/$USERNAME/wifipumpkin3
$ cd wifipumpkin3
-
Setup the virtual environment with dependencies and tools, follow the steps to install the tool.
-
Format your code using Black:
$ make format
We actively welcome your pull requests. Send the pull requests on branch inbox
and now wait the answer.
- If you've added code that should be tested, add unit tests.
- update the documentation if necessary.
- Ensure the test suite passes if you add a new unit tests.
We use GitHub issues to track public bugs. Please ensure your description is clear and has sufficient instructions to be able to reproduce the issue.
By contributing to Wp3, you agree that your contributions will be licensed
under the LICENSE
file in the root directory of this source tree.