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

GHA: Fix condition for duplicate checks post-merge #648

Conversation

BbolroC
Copy link
Member

@BbolroC BbolroC commented Aug 2, 2024

Despite #644, duplicate checks are still being triggered post-merge. The following condition seemed intuitive:

  • github.event_name != 'push' || github.event.pull_request.merged == false

But it turns out that pull_request.merged is still false on merge, which allows the job to proceed.
(see https://github.com/BbolroC/cc-guest-components/actions/runs/10215060610/workflow)

This commit focuses solely on github.event_name != 'push', which is true on merge.
(see https://github.com/BbolroC/cc-guest-components/actions/runs/10215137827/workflow)

Signed-off-by: Hyounggyu Choi [email protected]

Despite confidential-containers#644, duplicate checks are still being triggered post-merge.
The following condition seemed intuitive:

- github.event_name != 'push' || github.event.pull_request.merged == false

But it turns out that `pull_request.merged` is still false on merge, which allows the job to proceed.
(see https://github.com/BbolroC/cc-guest-components/actions/runs/10215060610/workflow)

This commit focuses solely on `github.event_name != 'push'`, which is true on merge.
(see https://github.com/BbolroC/cc-guest-components/actions/runs/10215137827/workflow)

Signed-off-by: Hyounggyu Choi <[email protected]>
@BbolroC BbolroC requested a review from sameo as a code owner August 2, 2024 12:11
@BbolroC BbolroC requested review from fitzthum and arronwy August 2, 2024 12:45
Copy link
Member

@fitzthum fitzthum left a comment

Choose a reason for hiding this comment

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

LGTM but maybe someone wants to keep these jobs?

@BbolroC
Copy link
Member Author

BbolroC commented Aug 2, 2024

Let’s see if anyone opposes this after the intended CI behavior occurs. Thanks! (maybe someone who wants to push something directly to main?)

@BbolroC BbolroC merged commit 4647ec5 into confidential-containers:main Aug 2, 2024
24 checks passed
@BbolroC BbolroC deleted the fix-if-condition-for-duplicated-check branch August 2, 2024 13:53
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.

2 participants