Enjoying WaSQL and want to get involved? Great! There are plenty of ways you can help out.
Please take a moment to review this document in order to make the contribution process easy and effective for everyone involved.
Following these guidelines helps to communicate that you respect the time of the developers managing and developing this open source project. In return, they should reciprocate that respect in addressing your issue or assessing patches and features.
The issue tracker is the preferred channel for changes: spelling mistakes, wording changes, new content and generally submitting pull requests, but please respect the following restrictions:
-
Please do not use the issue tracker for personal support requests (use Stack Overflow or IRC).
-
Please do not derail or troll issues. Keep the discussion on topic and respect the opinions of others.
Pull requests are a great way to add new content to WaSQL, as well as updating any browser issues or other style changes. Pretty much any sort of change is accepted if seen as constructive.
Adhering to the following this process is the best way to get your work included in the project:
-
Fork WaSQL. If you don't have an SSH key yet, create one and add it to your profile.
ssh-keygen
-
If you have not downloade WaSQL yet, get the code:
git clone [email protected]:yourusername/v2.git
-
Change directory into v2 and set the URL.
git remote set-url origin [email protected]:yourusername/v2.git
-
Add an remote to track WaSQL. (It doesn't have to be named "upstream").
git remote add upstream [email protected]:WaSQL/v2.git
-
To get the latest code:
git fetch upstream
git merge upstream upstream/master
-
Add your changes to the stage. You may have to enter your email and name.
-
Commit your changes.
git commit -m "Your message here."
-
Push your changes to your repository.
git push -u origin master
-
On the repository you are adding to, create a pull request and wait for your changes to be approved.
By submitting a pull request to this repository, you agree to follow our code of conduct
All content is completely free now, and always will be.
- Use American English spelling (primary English repo only)
- Use tabs to indent text; do not use spaces
- Wrap all text to 120 characters
- Code samples should adhere to PSR-1 or higher
- Use GitHub Flavored Markdown for all content
- Use language agnostic urls when referring to external websites such as the php.net manual