|
1 | | -# Contributing to ScrapeGraphAI |
2 | | - |
3 | | -Thank you for your interest in contributing to **ScrapeGraphAI**! We welcome contributions from the community to help improve and grow the project. This document outlines the guidelines and steps for contributing. |
4 | | - |
5 | | -## Table of Contents |
6 | | - |
7 | | -- [Getting Started](#getting-started) |
8 | | -- [Contributing Guidelines](#contributing-guidelines) |
9 | | -- [Code Style](#code-style) |
10 | | -- [Submitting a Pull Request](#submitting-a-pull-request) |
11 | | -- [Reporting Issues](#reporting-issues) |
12 | | -- [License](#license) |
13 | | - |
14 | | -## Getting Started |
15 | | - |
16 | | -To get started with contributing, follow these steps: |
17 | | - |
18 | | -1. Fork the repository on GitHub **(FROM pre/beta branch)**. |
19 | | -2. Clone your forked repository to your local machine. |
20 | | -3. Install the necessary dependencies from requirements.txt or via pyproject.toml as you prefere :). |
21 | | -4. Make your changes or additions. |
22 | | -5. Test your changes thoroughly. |
23 | | -6. Commit your changes with descriptive commit messages. |
24 | | -7. Push your changes to your forked repository. |
25 | | -8. Submit a pull request to the pre/beta branch. |
26 | | - |
27 | | -N.B All the pull request to the main branch will be rejected! |
28 | | - |
29 | | -## Contributing Guidelines |
30 | | - |
31 | | -Please adhere to the following guidelines when contributing to ScrapeGraphAI: |
32 | | - |
33 | | -- Follow the code style and formatting guidelines specified in the [Code Style](#code-style) section. |
34 | | -- Make sure your changes are well-documented and include any necessary updates to the project's documentation and requirements if needed. |
35 | | -- Write clear and concise commit messages that describe the purpose of your changes and the last commit before the pull request has to follow the following format: |
36 | | - - `feat: Add new feature` |
37 | | - - `fix: Correct issue with existing feature` |
38 | | - - `docs: Update documentation` |
39 | | - - `style: Improve formatting and style` |
40 | | - - `refactor: Restructure code` |
41 | | - - `test: Add or update tests` |
42 | | - - `perf: Improve performance` |
43 | | -- Be respectful and considerate towards other contributors and maintainers. |
44 | | - |
45 | | -## Code Style |
46 | | - |
47 | | -Please make sure to format your code accordingly before submitting a pull request. |
48 | | - |
49 | | -### Python |
50 | | - |
51 | | -- [Style Guide for Python Code](https://www.python.org/dev/peps/pep-0008/) |
52 | | -- [Google Python Style Guide](https://google.github.io/styleguide/pyguide.html) |
53 | | -- [The Hitchhiker's Guide to Python](https://docs.python-guide.org/writing/style/) |
54 | | -- [Pylint style of code for the documentation](https://pylint.pycqa.org/en/1.6.0/tutorial.html) |
55 | | - |
56 | | -## Submitting a Pull Request |
57 | | - |
58 | | -To submit your changes for review, please follow these steps: |
59 | | - |
60 | | -1. Ensure that your changes are pushed to your forked repository. |
61 | | -2. Go to the main repository on GitHub and navigate to the "Pull Requests" tab. |
62 | | -3. Click on the "New Pull Request" button. |
63 | | -4. Select your forked repository and the branch containing your changes. |
64 | | -5. Provide a descriptive title and detailed description for your pull request. |
65 | | -6. Reviewers will provide feedback and discuss any necessary changes. |
66 | | -7. Once your pull request is approved, it will be merged into the pre/beta branch. |
67 | | - |
68 | | -## Reporting Issues |
69 | | - |
70 | | -If you encounter any issues or have suggestions for improvements, please open an issue on the GitHub repository. Provide a clear and detailed description of the problem or suggestion, along with any relevant information or steps to reproduce the issue. |
71 | | - |
72 | | -## License |
73 | | - |
74 | | -ScrapeGraphAI is licensed under the **MIT License**. See the [LICENSE](LICENSE) file for more information. |
75 | | -By contributing to this project, you agree to license your contributions under the same license. |
76 | | - |
77 | | -ScrapeGraphAI uses code from the Langchain |
78 | | -frameworks. You find their original licenses below. |
79 | | - |
80 | | -LANGCHAIN LICENSE |
81 | | -https://github.com/langchain-ai/langchain/blob/master/LICENSE |
82 | | - |
83 | | -Can't wait to see your contributions! :smile: |
| 1 | +# Contributing to ScrapeGraphAI 🚀 |
| 2 | + |
| 3 | +Hey there! Thanks for checking out **ScrapeGraphAI**! We're excited to have you here! 🎉 |
| 4 | + |
| 5 | +## Quick Start Guide 🏃♂️ |
| 6 | + |
| 7 | +1. Fork the repository from the **pre/beta branch** 🍴 |
| 8 | +2. Clone your fork locally 💻 |
| 9 | +3. Install uv (if you haven't): |
| 10 | + ```bash |
| 11 | + curl -LsSf https://astral.sh/uv/install.sh | sh |
| 12 | + ``` |
| 13 | +4. Run `uv sync` (creates virtual env & installs dependencies) ⚡ |
| 14 | +5. Run `uv run pre-commit install` 🔧 |
| 15 | +6. Make your awesome changes ✨ |
| 16 | +7. Test thoroughly 🧪 |
| 17 | +8. Push & open a PR to the pre/beta branch 🎯 |
| 18 | + |
| 19 | +## Contribution Guidelines 📝 |
| 20 | + |
| 21 | +Keep it clean and simple: |
| 22 | +- Follow our code style (PEP 8 & Google Python Style) 🎨 |
| 23 | +- Document your changes clearly 📚 |
| 24 | +- Use these commit prefixes for your final PR commit: |
| 25 | + ``` |
| 26 | + feat: ✨ New feature |
| 27 | + fix: 🐛 Bug fix |
| 28 | + docs: 📚 Documentation |
| 29 | + style: 💅 Code style |
| 30 | + refactor: ♻️ Code changes |
| 31 | + test: 🧪 Testing |
| 32 | + perf: ⚡ Performance |
| 33 | + ``` |
| 34 | +- Be nice to others! 💝 |
| 35 | + |
| 36 | +## Need Help? 🤔 |
| 37 | + |
| 38 | +Found a bug or have a cool idea? Open an issue and let's chat! 💬 |
| 39 | + |
| 40 | +## License 📜 |
| 41 | + |
| 42 | +MIT Licensed. See [LICENSE](LICENSE) file for details. |
| 43 | + |
| 44 | +Let's build something amazing together! 🌟 |
0 commit comments