generated from actions/typescript-action
-
Notifications
You must be signed in to change notification settings - Fork 260
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
Document usage in a merge queue #183
Comments
andreaangiolillo
added a commit
to mongodb/terraform-provider-mongodbatlas
that referenced
this issue
Nov 3, 2023
github-merge-queue bot
pushed a commit
to mongodb/terraform-provider-mongodbatlas
that referenced
this issue
Nov 3, 2023
…eue (#1590) * chore: add acceptance tests and migration tests to report in merge queue * fix based on dorny/paths-filter#183
github-merge-queue bot
pushed a commit
to mongodb/terraform-provider-mongodbatlas
that referenced
this issue
Nov 3, 2023
…eue (#1590) * chore: add acceptance tests and migration tests to report in merge queue * fix based on dorny/paths-filter#183 * fix
Draft
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm using this action in a merge queue. I'm not sure I've gotten all the details right just yet, but I think it works.
Merge queues are still in beta: https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue
The main issue I ran into was that there was no git repository available by default, like you get on the
pull_request
event. I'm currently doing this:The text was updated successfully, but these errors were encountered: