Skip to content

Commit a32b3fe

Browse files
authored
docs: add about section to documentation (#50)
1 parent fa76702 commit a32b3fe

File tree

5 files changed

+79
-7
lines changed

5 files changed

+79
-7
lines changed

docs/about/changelog.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
2+
--8<-- "CHANGELOG.md"

docs/about/contact.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
# Contact us
2+
3+
Hey 👋 My name is Mateusz, and I'm a lead maintainer of db-ally.
4+
5+
6+
7+
You can contact me directly at [[email protected]](mailto:[email protected])
8+

docs/about/contributing.md

Lines changed: 64 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,64 @@
1+
# Contributing
2+
3+
We are happy to see you here! 🚀
4+
5+
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:
62+
```
63+
feat!: change collection.ask method API
64+
```

docs/roadmap.md renamed to docs/about/roadmap.md

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,3 @@
1-
---
2-
hide:
3-
- navigation
4-
---
5-
61
# Roadmap
72

83
db-ally is actively developed and maintained by a core team at [deepsense.ai](https://deepsense.ai) and a community of contributors.

mkdocs.yml

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -73,8 +73,11 @@ nav:
7373
- Embeddings:
7474
- reference/embeddings/index.md
7575
- reference/embeddings/litellm.md
76-
- Roadmap: roadmap.md
77-
76+
- About:
77+
- about/roadmap.md
78+
- about/contributing.md
79+
- about/changelog.md
80+
- about/contact.md
7881
theme:
7982
name: material
8083
icon:

0 commit comments

Comments
 (0)