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

Add merge_group event trigger to GHA daily workflow #1996

Merged
merged 2 commits into from
Feb 24, 2023

Conversation

bandish-shah
Copy link
Contributor

What does this PR do?

This PR modifies the daily.yaml workflow by adding the merge_group event trigger and removing the push trigger for the dev branch. Merge queues were just enabled for dev so the intent is that the daily workflow will run on PR's pushed to the merge queue. For more information on merge queues, please see:
https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request-with-a-merge-queue

The daily workflow is now triggered as follows:

  • Run workflow on merge_group event
  • Run workflow on pushes to main and release branches
  • Run workflow at 2:30am every day on dev
  • Run workflow manually

Before submitting

* Run workflow on pushes to main and release branches
* Run workflow at 2:30am every day on dev
* Run workflow manually
* Removed run on push to dev
@bandish-shah bandish-shah requested a review from a team as a code owner February 23, 2023 23:59
Copy link
Contributor

@mvpatel2000 mvpatel2000 left a comment

Choose a reason for hiding this comment

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

Where do we check status if it's not on dev commit history for merge queues?

@mvpatel2000 mvpatel2000 self-requested a review February 24, 2023 00:04
@bandish-shah
Copy link
Contributor Author

Where do we check status if it's not on dev commit history for merge queues?

We're about to find out!

@bandish-shah bandish-shah added this pull request to the merge queue Feb 24, 2023
@bandish-shah
Copy link
Contributor Author

@mvpatel2000 after clicking "Merge when ready" and the confirmation, looks like the PR gets added to the merge queue which is here:
https://github.com/mosaicml/composer/queue/dev

In this case, it started running the daily immediately. It's currently configured to run up to 3 PR's concurrently and merge after 15 minutes if no other PR's are submitted.

@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to no response for status checks Feb 24, 2023
@bandish-shah bandish-shah added this pull request to the merge queue Feb 24, 2023
@bandish-shah bandish-shah removed this pull request from the merge queue due to a manual request Feb 24, 2023
@bandish-shah bandish-shah added this pull request to the merge queue Feb 24, 2023
@bandish-shah bandish-shah removed this pull request from the merge queue due to a manual request Feb 24, 2023
@bandish-shah bandish-shah added this pull request to the merge queue Feb 24, 2023
Merged via the queue into mosaicml:dev with commit f4c7abd Feb 24, 2023
@bandish-shah bandish-shah deleted the bandish/merge_queues branch February 24, 2023 03:17
bandish-shah pushed a commit to bandish-shah/composer that referenced this pull request Feb 24, 2023
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