PluginProbe ʕ •ᴥ•ʔ
WooCommerce Square / 5.4.2
WooCommerce Square v5.4.2
5.4.3 5.4.2 5.4.1 5.4.0 trunk 1.0.25 1.0.26 1.0.27 1.0.28 1.0.29 1.0.30 1.0.31 1.0.32 1.0.33 1.0.34 1.0.35 1.0.36 1.0.37 1.0.38 2.0.0 2.0.1 2.0.2 2.0.3 2.0.4 2.0.5 2.0.6 2.0.7 2.0.8 2.1.0 2.1.1 2.1.2 2.1.3 2.1.4 2.1.5 2.1.6 2.2.0 2.2.1 2.2.2 2.2.3 2.2.4 2.2.5 2.3.0 2.3.1 2.3.2 2.3.3 2.3.4 2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.5.3 2.6.0 2.7.0 2.8.0 2.9.0 2.9.1 3.0.0 3.0.1 3.0.2 3.0.3 3.1.0 3.2.0 3.3.0 3.4.0 3.4.1 3.4.2 3.5.0 3.6.0 3.6.1 3.7.0 3.7.1 3.8.0 3.8.1 3.8.2 3.8.3 3.9.0 4.0.0 4.1.0 4.2.0 4.2.1 4.2.2 4.2.3 4.3.0 4.3.1 4.3.2 4.4.0 4.4.1 4.4.2 4.5.0 4.5.1 4.5.2 4.6.0 4.6.1 4.6.2 4.6.3 4.6.4 4.7.0 4.7.1 4.7.2 4.7.3 4.7.4 4.8.0 4.8.1 4.8.2 4.8.3 4.8.4 4.8.5 4.8.6 4.8.7 4.8.8 4.9.0 4.9.1 4.9.2 4.9.3 4.9.4 4.9.5 4.9.6 4.9.7 4.9.8 4.9.9 5.0.0 5.0.1 5.1.0 5.1.1 5.1.2 5.2.0 5.3.0 5.3.1 5.3.2 5.3.3
woocommerce-square / vendor / apimatic / core / CONTRIBUTING.md
woocommerce-square / vendor / apimatic / core Last commit date
src 1 year ago CONTRIBUTING.md 1 year ago LICENSE 2 years ago README.md 1 year ago composer.json 1 year ago composer.lock 1 year ago phpcs-ruleset.xml 3 years ago phpunit.xml 2 years ago
CONTRIBUTING.md
62 lines
1 # Contributing to apimatic/core-lib-php
2
3 Thank you for your interest in contributing! 🎉 Your contributions help make this project better. We value open-source contributions to this library, please take a few minutes to review this guide before you start.
4
5 ---
6
7 ## 💡 How to Contribute
8
9 ### 📌 1. Reporting Issues
10
11 - Search existing issues before opening a new one.
12 - Use a **descriptive title** and provide clear steps to reproduce.
13 - Include relevant logs, screenshots, or error messages.
14
15 ### 🔧 2. Making Changes
16
17 #### Step 1: Create a Branch
18
19 - Create a new branch from `master`:
20 ```sh
21 git checkout -b your-feature-name
22 ```
23
24 #### Step 2: Make Your Changes
25
26 - Follow the project's **coding standards**.
27 - Add **unit tests** if applicable.
28 - Ensure your changes **do not break existing functionality**.
29
30 #### Step 3: Commit Changes
31
32 - Use clear and descriptive commit messages:
33 ```sh
34 git commit -m "feat: Add feature description"
35 ```
36
37 #### Step 4: Push & Open a PR
38
39 - Push your branch:
40 ```sh
41 git push origin your-feature-name
42 ```
43 - Open a **Pull Request (PR)** on GitHub:
44 - Provide a clear **description** of the changes.
45 - Mention related **issue numbers**.
46 - Request a **review** from maintainers.
47 - Make sure your changes clear all the **PR Checks**.
48
49 ---
50
51 ## 📜 License
52
53 By contributing, you agree that your contributions will be licensed under the project's [](LICENSELICENSE](LICENSE](LICENSE).
54
55 ---
56
57 💬 **Questions?**
58 If you need help, feel free to open issues, we will be happy to help.
59
60 Happy Coding! 🚀
61
62