We provide the extensions, settings, and tasks for VSCode in the .vscode
folder.
- Install the extensions
cd .vscode && sh install_extensions.sh && cd ..
- Open the project in VSCode
code .
- Open terminals
In VSCode, runCtrl+Shift+B
to open two terminal windows: a localbash
one and aviadot_2
container one.
To run tests, you may need to set up some environment variables or the viadot config. You can find all the required environment variables in the tests' dotenv file, and all the required viadot config settings in the config file. We're working on making this process easier, so only one of these can be used.
- code should be formatted with
black
using default settings (easiest way is to use the VSCode extension) - imports should be sorted using
isort
- commit messages should:
- begin with an emoji
- start with one of the following verbs, capitalized, immediately after the summary emoji: "Add", "Update", "Remove", "Fix", "Rename", and, sporadically, other ones, such as "Upgrade", "Downgrade", or whatever you find relevant for your particular situation
- contain a useful summary of what the commit is doing See this article to understand basics of naming commits
- Fork the repo
- Install and configure
viadot
Note: In order to run tests, you will also need to install dev dependencies in theviadot_2
container withpip install requirements-dev.txt
- Checkout a new branch
Make sure that your base branch is
git checkout -b <name>
2.0
! - Add your changes
Note: See out Style Guidelines for more information about commit messages and PR names - Test the changes locally
docker exec -it viadot_2 sh -c "pytest"
- Sync your fork with the
dyvenia
repogit remote add upstream https://github.com/dyvenia/viadot.git git fetch upstream 2.0 git checkout 2.0 git rebase upstream/2.0
- Push the changes to your fork
git push --force
- Submit a PR into the
2.0
branch. Make sure to read & check all relevant checkboxes in the PR template!