You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking for a way to contribute to db-ally? Check-out our issues with a [good first issue](https://github.com/deepsense-ai/db-ally/labels/good%20first%20issue) label.
6
+
7
+
You can also suggest new features or report bugs by [opening an issue](https://github.com/deepsense-ai/db-ally/issues).
8
+
9
+
## Contributor guide
10
+
11
+
1. Fork the repository and clone it locally.
12
+
13
+
2. Install the development dependencies:
14
+
15
+
```bash
16
+
./setup_dev_env.sh
17
+
```
18
+
19
+
It will create a virtual environment and install all necessary dependencies.
20
+
Make sure that you have Python 3.8 or higher installed on your machine.
21
+
22
+
3. Make your changes and write tests for them if necessary.
23
+
24
+
4. Run the tests:
25
+
26
+
```bash
27
+
pytest tests/
28
+
```
29
+
30
+
5. If creating new feature, don't forget to update the documentation.
31
+
32
+
You can run the documentation locally by executing:
33
+
34
+
```bash
35
+
mkdocs serve
36
+
```
37
+
38
+
6. Push your changes to your fork and create a pull request from there.
39
+
40
+
41
+
## Commits convention
42
+
43
+
We use [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) for our commit messages.
44
+
45
+
In practice that means that each commit message should be prefixed with one of the following types:
46
+
47
+
```
48
+
feat: A new feature
49
+
fix: A bug fix
50
+
docs: Documentation only changes
51
+
refactor: A code change that neither fixes a bug nor adds a feature
52
+
test: Adding missing tests or correcting existing tests
53
+
chore: Changes to the build process or repo setup
54
+
```
55
+
56
+
For example:
57
+
```
58
+
feat: add text2sql views code generation
59
+
```
60
+
61
+
Breaking changes should be indicated by adding an exclamation mark to the prefix:
0 commit comments