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

Switch omes to post-merge #1583

Merged
merged 1 commit into from
Aug 8, 2024
Merged

Switch omes to post-merge #1583

merged 1 commit into from
Aug 8, 2024

Conversation

Sushisource
Copy link
Member

No description provided.

@Sushisource Sushisource requested a review from a team as a code owner August 8, 2024 18:01
on:
push:
branches:
- master
Copy link
Contributor

Choose a reason for hiding this comment

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

The GitHub jobs suggest something more complicated. But perhaps on push master is a superset of close and merge PR. (Also the GitHub docs thing looks like it would trigger on a merge to non-master/main).

Copy link
Member Author

Choose a reason for hiding this comment

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

This is what we use virtually everywhere for workflows like this

Copy link
Contributor

@dandavison dandavison left a comment

Choose a reason for hiding this comment

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

LGTM!

@Sushisource Sushisource merged commit 2927574 into master Aug 8, 2024
14 checks passed
@Sushisource Sushisource deleted the omes-post-merge branch August 8, 2024 18:54
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.

3 participants