multiple-amethyst•2mo ago

Getting started with contributing

For me to get started I would have to first read the guidelines and then clone the repo and find issues I want to fix, then I should be good to go?

15 Replies

adverse-sapphire•2mo ago

Hey @ProgrammerOS, you are more or less correct 🙂 You can have a look at our contributing guide: https://github.com/ComposioHQ/composio/blob/master/CONTRIBUTING.md And development guide (for python): https://github.com/ComposioHQ/composio/blob/master/python/docs/development.md

GitHub

composio/CONTRIBUTING.md at master · ComposioHQ/composio

Composio equips agents with well-crafted tools empowering them to tackle complex tasks - ComposioHQ/composio

GitHub

composio/python/docs/development.md at master · ComposioHQ/composio

Composio equips agents with well-crafted tools empowering them to tackle complex tasks - ComposioHQ/composio

adverse-sapphire•2mo ago

First you need to read the guidelines -> fork the repo -> clone it -> do your changes -> push in your repo -> raise a PR Let me know if you want any other help @ProgrammerOS 🙌

multiple-amethyst•2mo ago

thank you so much for the help

adverse-sapphire•2mo ago

It was my pleasure to help you 😄

multiple-amethyst•2mo ago

i just forked and cloned the repo, how would i be able to run the project itself @thatsmeadarsh would it be the make env and pipenv shell (not sure where to run it in the project repo specifically)?

adverse-sapphire•2mo ago

You need to install pipenv, then go inside python/ and run make env Note: if you are using windows, install Ubuntu Shell

multiple-amethyst•2mo ago

when i got to the point i ran make env, it ran all commands and when it tried to make the virtual envrionment, it kept looping over and over that it failed to do so

adverse-sapphire•2mo ago

Can you run it once using sudo make env??

multiple-amethyst•2mo ago

same issue

adverse-sapphire•2mo ago

Okay, I got the issue telling you in some time

multiple-amethyst•2mo ago

let me know as soon as possible

adverse-sapphire•2mo ago

Sure, thank you for your patience!!

adverse-sapphire•2mo ago

@ProgrammerOS The issue is that pipenv is trying to make the virtualenv in a root directory. We have a few possible options: 1. Use the WORKON_HOME environment variable: You can set this to a directory where you have write permissions to make the virtualenv. For example:

   export WORKON_HOME=$HOME/.virtualenvs
2. Use the PIPENV_VENV_IN_PROJECT environment variable:
   This will create the virtual environment in a `.venv` directory within your project directory:

   export WORKON_HOME=$HOME/.virtualenvs
2. Use the PIPENV_VENV_IN_PROJECT environment variable:
   This will create the virtual environment in a `.venv` directory within your project directory:

export PIPENV_VENV_IN_PROJECT=1

3. Use the --venv option when running pipenv:

3. Use the --venv option when running pipenv:

pipenv --venv /path/to/your/venv/directory

4. Modify the Pipfile to specify a custom virtual environment location:
   Add this to your Pipfile:

4. Modify the Pipfile to specify a custom virtual environment location:
   Add this to your Pipfile:

[virtualenvs] location = "/path/ Try to follow anyone and run the command again. Let me know if you still face the issue.

multiple-amethyst•2mo ago

I've tried the last two methods, --venv option told me an error "no such command path" and the last method gave the same issue as the original post Also im not even sure about pipenv itself because all I was able to do so far was "make env" and that original issue i posted came up so pipenv shell maybe might not work since the virtualenv wasn't created nvm got it to work now how exactly would i be able to run the application itself after i ran pipenv shell i was thinking make login or make publish

Soham•2mo ago

No so once that is installed you can follow quickstart on docs.composio.dev To get started. Then you can try different tools. Especially try running swe agent for example