Gitlab DBT example inconsistencies for a reason?

[stevenayers]

Under branch deployment for preparing a DBT project, there is this:

dagster-cloud-action/gitlab/dbt/serverless-ci-dbt.yml

Lines 36 to 45 in b3e7bec

	- pip install pip --upgrade
	- cd $DAGSTER_DBT_PROJECT_DIR/$DAGSTER_DBT_PROJECT_NAME
	- pip install . MarkupSafe==2.0.1 'click>8.1.0' 'Jinja2>3.0.0'
	- pip install pyOpenSSL --upgrade
	- cd -
	- which rsync || ( apt-get update -y && apt-get -y install rsync )
	- rsync -avz --exclude $DAGSTER_DBT_PROJECT_NAME --exclude .git $DAGSTER_DBT_PROJECT_DIR/ $DAGSTER_DBT_PACKAGE_DATA_DIR
	- dbt deps --project-dir $DAGSTER_DBT_PACKAGE_DATA_DIR --profiles-dir $DAGSTER_DBT_PACKAGE_DATA_DIR
	- dbt parse --project-dir $DAGSTER_DBT_PACKAGE_DATA_DIR --profiles-dir $DAGSTER_DBT_PACKAGE_DATA_DIR
	- rm $DAGSTER_DBT_PACKAGE_DATA_DIR/target/partial_parse.msgpack

Should it not use the same method of prepare that the main branch is using?

dagster-cloud-action/gitlab/dbt/serverless-ci-dbt.yml

Lines 82 to 85 in b3e7bec

	- pip install pip --upgrade
	- cd $DAGSTER_DBT_PROJECT_DIR/$DAGSTER_DBT_PROJECT_NAME
	- pip install . --upgrade --upgrade-strategy eager
	- dagster-dbt project prepare-and-package --file $DAGSTER_DBT_PROJECT_NAME/project.py

I say this because branch_deployments.yml for the GitHub example do this:

dagster-cloud-action/github/serverless/dbt/branch_deployments.yml

Lines 66 to 72 in b3e7bec

	run: |
	python -m pip install pip --upgrade
	cd project-repo/${{ env.DAGSTER_PROJECT_NAME }}
	pip install . --upgrade --upgrade-strategy eager
	dagster-dbt project prepare-and-package --file ${{ env.DAGSTER_PROJECT_NAME }}/project.py
	# The cli command below can be used to manage syncing the prod manifest to branches if state_path is set on the DbtProject
	# dagster-cloud ci dagster-dbt project manage-state --file ${{ env.DAGSTER_PROJECT_NAME }}/project.py