Skip to content

Latest commit

 

History

History
56 lines (42 loc) · 2.09 KB

CONTRIBUTING.md

File metadata and controls

56 lines (42 loc) · 2.09 KB

Contibution guide

Development Setup

Requires Python 3.9-3.12.

pip install -e .[tests,bigquery,docker,datahub,gcs,s3]
pip install -r requirements-dev.txt
pre-commit install

Note: A dbt adapter extra (e.g., bigquery, snowflake) is required because dbt-core is provided as a transitive dependency. Any adapter can be used for development.

Running Tests

# Run all tests
pytest --cov data_pipelines_cli --cov-report term-missing --ignore=venv

# Run specific test
pytest tests/test_dbt_utils.py::test_specific_function

# Test all Python versions with tox
tox

# Test specific Python version
tox -e py310

PR Guidelines

  1. Fork branch from develop.
  2. Ensure to provide unit tests for new functionality.
  3. Install dev requirements: pip install -r requirements-dev.txt and setup a hook: pre-commit install.
  4. Run tox to verify all Python versions pass.
  5. Update documentation accordingly.
  6. Update changelog according to "Keep a changelog" guidelines.
  7. Squash changes with a single commit as much as possible and ensure verbose PR name.
  8. Open a PR against the develop branch.

We reserve the right to take over and modify or abandon PRs that do not match the workflow or are abandoned.

Release workflow

  1. Create the release candidate:
    • Go to the Prepare release action.
    • Click "Run workflow"
    • Enter the part of the version to bump (one of <major>.<minor>.<patch>). Minor (x.x.x) is a default.
  2. If the workflow has run sucessfully:
    • Go to the newly openened PR named Release candidate <version>
    • Check that changelog and version have been properly updated. If not pull the branch and apply manual changes if necessary.
    • Merge the PR to main
  3. Checkout the Publish workflow to see if:
    • The package has been uploaded on PyPI successfully
    • The changes have been merged back to develop