Release v0.2.2

bugfix: correct check for empty env var (#9)

# Pull Request

## Checklist
- [x] Have you read Digital Catapult's [Code of
Conduct](https://github.com/digicatapult/.github/blob/main/CODE_OF_CONDUCT.md)?
- [x] I have performed a self-review of my own code.
- [x] I have commented my code, particularly in hard-to-understand
areas.
- [ ] I have made corresponding changes to the documentation.
- [x] My changes generate no new warnings.
- [ ] I have added tests that prove my fix is effective or that my
feature works.
- [ ] New and existing unit tests pass locally with my changes.

## PR Type

- [x] Bug Fix


## Linked tickets

<!-- If this PR is linked to a JIRA ticket or Github Issue, please
provide the ticket URL here. -->

## High level description

The check for empty environment variable was failing because the env
variables are passed as empty strings instead of None.

## Detailed description

<!-- A detailed description of the feature and if possible describe how
has been implemented. -->


## Describe alternatives you've considered

<!-- A clear and concise description of the alternative solutions you've
considered. Be sure to explain why the existing customisability isn't
suitable for this feature. -->

## Operational impact

<!--- A description of any operational considerations associated with
the change. Is there anything in particular we should be looking at when
deploying the change to make sure it is working as intended. If
something goes wrong will any special actions be needed to revert the
change. -->

## Additional context

<!-- Add any other context or screenshots about the feature request
here. -->

Latest Release v0.2.2

Commits

• correct check for empty env var (#9) #9 (Renjith Baby)

Release v0.2.1

Feature/dvc with aws conn (#8)

# Pull Request

## Checklist
- [x] Have you read Digital Catapult's [Code of
Conduct](https://github.com/digicatapult/.github/blob/main/CODE_OF_CONDUCT.md)?
- [x] I have performed a self-review of my own code.
- [x] I have commented my code, particularly in hard-to-understand
areas.
- [x] I have made corresponding changes to the documentation.
- [x] My changes generate no new warnings.
- [ ] I have added tests that prove my fix is effective or that my
feature works.
- [ ] New and existing unit tests pass locally with my changes.

## PR Type

Please delete options that are irrelevant.

- [x] Feature

## Linked tickets

<!-- If this PR is linked to a JIRA ticket or Github Issue, please
provide the ticket URL here. -->

## High level description

<!-- One paragraph explanation of the feature. -->

## Detailed description

<!-- A detailed description of the feature and if possible describe how
has been implemented. -->


## Describe alternatives you've considered

<!-- A clear and concise description of the alternative solutions you've
considered. Be sure to explain why the existing customisability isn't
suitable for this feature. -->

## Operational impact

<!--- A description of any operational considerations associated with
the change. Is there anything in particular we should be looking at when
deploying the change to make sure it is working as intended. If
something goes wrong will any special actions be needed to revert the
change. -->

## Additional context

<!-- Add any other context or screenshots about the feature request
here. -->

Release v0.2.0

Using dockerhub and ghcr (#7)

# Pull Request

## Checklist
- [X] Have you read Digital Catapult's [Code of
Conduct](https://github.com/digicatapult/.github/blob/main/CODE_OF_CONDUCT.md)?
- [X] I have performed a self-review of my own code.
- [X] I have commented my code, particularly in hard-to-understand
areas.
- [X] I have made corresponding changes to the documentation.
- [ ] My changes generate no new warnings.
- [ ] I have added tests that prove my fix is effective or that my
feature works.
- [ ] New and existing unit tests pass locally with my changes.

## PR Type

Please delete options that are irrelevant.


- [X] Chore

## Linked tickets

N/A

## High level description

Adds ability to push to dockerhub

## Detailed description

Alters the publish step so that we release container artifacts to
dockerhub as well as GHCR so people can pull without requiring GHCR
authentication.


## Describe alternatives you've considered

N/A

## Operational impact

N/A

## Additional context

N/A

Release v0.1.4

update version increment and add unit tests for the same (#6)

* update version increment and add unit tests for the same

* increment version

Release v0.1.3

introduce env var for dvc endpoint url (#5)

* introduce env var for dvc endpoint url

* increment version

Release v0.1.2

update readme - remove unused docker compose command (#4)

* update readme - remove unused docker compose command

* undo code changes - keeping for another pr

* increment version

* fix readme formatting

Release v0.1.1

dvc push - fix and readme update (#3)

* fix git checkout when branch doesn't exist

* fix the tag with data- prefix

* fix git checkout function

* update version

* update version check workflow

* update dvc push to s3 minio bucket

* update readme

Release 0.1.0

Feature/data ingestion (#1)

* add initial repo skeleton

* add pytest

* add basic pipeline with git - no remote set

* add data to dvc

* complete pipeline till data split

* fix logging mistake

* add details of the manual dvc push in the readme

* add data push module

* reformat

* add unit and integration tests

* review changes - git workflows

* update the dvc integration test