Skip to content
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

Compare beginning and end of whole PR when determining if dag-only #53

Merged
merged 4 commits into from
Feb 21, 2024

Conversation

collinmcnulty
Copy link
Contributor

Based on @cdabella's demo, swapping comparison of only the most recent commit for a comparison of the whole PR.

Closes #52

action.yaml Outdated
@@ -264,7 +264,7 @@ runs:
- name: Get Deployment Type
run: |
cd ${{ inputs.root-folder }}
files=$(git diff --name-only HEAD^..HEAD)
files=$(git diff --name-only ${{ github.event.before }} ${{ github.event.after }} | grep '^deployments/' | awk -F/ '{print $2}' | sort -u)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the purpose of the grep/awk/sort?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There wasn't, removed now

@@ -264,7 +264,7 @@ runs:
- name: Get Deployment Type
run: |
cd ${{ inputs.root-folder }}
files=$(git diff --name-only HEAD^..HEAD)
files=$(git diff --name-only ${{ github.event.before }} ${{ github.event.after }})
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure if this will work with this change alone, because the clone on line 90 only fetches with a depth of two commits. Some options may be to fetch a reasonably large number of commits, say 50, which leaves a small risk of missing some in extreme cases, or to fetch all commits (I think the default if you don't specify fetch-depth, would need to be check that) which could be slow on very large repos, or to somehow use the push event payload to figure out the required fetch depth for that push (not sure if this is possible, but it would be the length of the commits list + 1).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only a single commit is fetched by default, for the ref/SHA that triggered the workflow. Set fetch-depth: 0 to fetch all history for all branches and tags. Refer here to learn which commit $GITHUB_SHA points to for different events.

https://github.com/actions/checkout

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we just run git fetch origin ${{ github.event.before }} after checkout?

- name: Fetch commit from before PR
run: |
get fetch origin ${{ github.event.before }}
shell: bash

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is probably not needed as you are not using any bash directives

action.yaml Outdated Show resolved Hide resolved
@sunkickr
Copy link
Contributor

can't really make a pre-release from the this branch so I'll have to merge and make a pre-release off main

@sunkickr sunkickr merged commit e7ee600 into astronomer:main Feb 21, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Rebase and Merge causes incorrect use of dag only deploy
4 participants