Skip to content

Commit a632d31

Browse files
committed
doc: add contribute.md and readme.md
1 parent d3ee5d7 commit a632d31

File tree

2 files changed

+199
-301
lines changed

2 files changed

+199
-301
lines changed

CONTRIBUTING.md

Lines changed: 90 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,90 @@
1+
# Contributing to TaskingAI
2+
3+
We welcome contributions from the community and are pleased to have you join us. This document will help you get started.
4+
5+
## Developing Locally with Poetry
6+
7+
[Poetry](https://python-poetry.org/) is a dependency management and packaging tool in Python that makes it easy to manage virtual environments. It's particularly useful when you need to test changes to the TaskingAI client in a local development setup.
8+
9+
Whether you're looking to fix a bug, add a new feature, or just improve the TaskingAI client, you'll want to be able to:
10+
11+
1. Test your changes in isolation from your system Python installation.
12+
2. See your changes reflected immediately in any local code that imports the TaskingAI client.
13+
3. Keep track of your changes in git to enable collaboration and code review through GitHub pull requests.
14+
15+
### Step 1: Fork and Clone the Repository
16+
17+
First, create a fork of the TaskingAI client repository on GitHub, and then clone your fork locally:
18+
19+
```bash
20+
git clone https://github.com/<your-username>/taskingai-python-client.git
21+
cd taskingai-python-client
22+
```
23+
24+
### Step 2: Install Poetry
25+
26+
You can install Poetry by following the instructions on [the official website](https://python-poetry.org/docs/).
27+
28+
### Step 3: Install Dependencies
29+
30+
Once Poetry is installed, you can install all the required dependencies by running:
31+
32+
```bash
33+
poetry install
34+
```
35+
36+
### Step 4: Activate the Virtual Environment
37+
38+
Enter the virtual environment shell created by Poetry:
39+
40+
```bash
41+
poetry shell
42+
```
43+
44+
Verify the setup:
45+
46+
```bash
47+
poetry env info
48+
```
49+
50+
### Step 5: Make Changes and Test
51+
52+
Now you can start making changes to the TaskingAI client. To test your changes, you may want to:
53+
54+
- Write unit tests.
55+
- Run the TaskingAI client in your local applications or Jupyter Notebooks.
56+
57+
### Step 6: Push Changes and Create a Pull Request
58+
59+
After making your changes, push them to your fork and [create a pull request](https://github.com/taskingai/taskingai-python-client/compare) on the original TaskingAI repository.
60+
61+
## Load Your Virtualenv in Another Shell
62+
63+
To use your development version of the TaskingAI client in another application or Jupyter Notebook:
64+
65+
### Get the Path to Your Virtualenv
66+
67+
Run:
68+
69+
```bash
70+
poetry env info --path
71+
```
72+
73+
### Activate Your Virtualenv
74+
75+
Source the `activate` script in your virtualenv:
76+
77+
```bash
78+
source <your-virtualenv-path>/bin/activate
79+
```
80+
81+
### Test Your Virtualenv
82+
83+
Create a test file in your TaskingAI client code directory and another in your second shell to verify that changes to the client are reflected immediately.
84+
85+
## Need Help?
86+
87+
If you have any questions or run into issues, please [file an issue](https://github.com/taskingai/taskingai-python-client/issues/new) on GitHub.
88+
89+
90+
Thank you for contributing to TaskingAI!

0 commit comments

Comments
 (0)