Add CI workflow

[emmyoop]

resolves #12

targetting copy-code-from-dbt-core since thats where the tests exist

testing, code quality and build are all separate. The build workflow is just a stub until we decide on the build tool. We can use it to both test the build works during regularly run CI as well as for the release process if needed.

Left to do

• Setting up code coverage. will do as part of Set up codecov in CI #16
• build workflow - this can be pushed off to Validate builds in CI and release #17 and is not blocking. Right now it works but lacks some validation after building. It should not block porting over the code.

[MichelleArk]

perhaps: pip freeze | grep dbt-common? it should return a non-zero exit code if no match is found. e.g.

❯ pip freeze | grep requests
❯ echo $?
1
❯ pip freeze | grep dbt-common
dbt-common @ file:///Users/michelleark/src/dbt-common
❯ echo $?
0

[MichelleArk]

Looks good! We can look into adding additional checks (e.g. mypy) to the pre-commit config but that can be done on the base PR. Here are the dbt-semantic-interfaces checks for reference: https://github.com/dbt-labs/dbt-semantic-interfaces/blob/main/.pre-commit-config.yaml

[emmyoop]

Agree. The code quality check will just run anything we set up in the config so we can play with it on the other branch.