-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle case when triggered event is a new branch or a tag push #90
Conversation
action.yaml
Outdated
DBT_DEPLOY=false | ||
|
||
# case when the triggered event is a new tag creation, then we would need to deploy the dbt project to be on the safe side |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: there is also a before null commit on pushing a new branch
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ohh yeah, good call to include that as well 👍
action.yaml
Outdated
DBT_DEPLOY=false | ||
|
||
# case when the triggered event is a new tag creation, then we would need to deploy the dbt project to be on the safe side |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: "on the safe side" is a bit vague. We should say that we have to deploy the dbt project (or image below) because we cannot determine that it does not need to be deployed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving ahead of comment nits
Description:
Fix the case when the before SHA for the triggered event is null (i.e. case when a new tag is pushed), in which case now we would do an image deploy and a dbt deploy (if configured), to be on the safe side.
Testing:
manually running the tests, since it is not straightforward to replicate the behavior in e2e tests. The below screenshot shows a run in a repo that had an "on tag" trigger event.
![Screenshot 2024-10-28 at 2 32 18 PM](https://private-user-images.githubusercontent.com/92356010/380644518-c198ab35-7456-4aa1-b0a7-0e6458969be9.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkyNzAwNjQsIm5iZiI6MTczOTI2OTc2NCwicGF0aCI6Ii85MjM1NjAxMC8zODA2NDQ1MTgtYzE5OGFiMzUtNzQ1Ni00YWExLWIwYTctMGU2NDU4OTY5YmU5LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjExVDEwMjkyNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWM0ZWExNmIzMmM4MTljMjQ3YjA0MjRmNGJlZjFmM2JjZjZjYTYzMGFkZjM3ZjcxYmQxMzA4ZGNlZGZhMGY4ZGEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.GkjLAh9NmjBPa4lLcBK8Hjjfu6NSLRW69FNitB0f6sg)
Reference: https://github.com/neel-astro/example-repo-update/actions/runs/11550491614/job/32145579388
Fixes: #82