~/.whale
subdirectory.~/.whale
directory to the provided git remote (replace <YOUR_GIT_REMOTE>
with your git address). This will add a .gitignore
file, add all files, and push to your git remote server.connections.yaml
file to your repo. If you'd like to avoid doing this, mv
your ~/.whale/config/connections.yaml
file elsewhere first and see Advanced usage.metadata.yml
), paste in the following file, then git add
, commit
, & push
to master.git pull --autostash --rebase
to occur programmatically. To do this, run the following command:is_git_etl_enabled: "true"
flag to the file located at ~/.whale/config/config.yaml
. This file can be accessed by running wh config
and manually edited at any point to turn the flag off.git
commands can be a bit dangerous, whale's file formatting ensures that this is done in debuggable and easily resolvable manner. Because the only local command run is the git pull --autostash --rebase
command, your personal edits will be saved as merge conflicts, still viewable in the respective files (and therefore, through wh
). If such conflicts arise, we will surface this to you through a warning when running wh
, and they should be simple to address.~/.whale
directory or the clone will fail.wh git-setup
is doing the following:git add . && git commit -m "Whale on our way" && git push
credentials.yaml
file in config/credentials.yaml
, and create a CI/CD pipeline that does the following (or use our github action above):~/.whale
on your CI/CD runner.pip install whalebuilder
python -c 'import whalebuilder as wh; wh.run()'
.import logging
and adjust the logging level).connections.yaml
file as a Github secret (named CONNECTIONS
in the example below), then echo this into the ~/.whale/config/connections.yaml
file. For example, with Github actions: