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 scaffolding DatabaseTrigger class #28801

Merged
merged 1 commit into from
Aug 21, 2022

Conversation

roji
Copy link
Member

@roji roji commented Aug 20, 2022

Part of #27588

@roji roji requested a review from a team August 20, 2022 12:14
@roji roji enabled auto-merge (squash) August 20, 2022 12:14
@roji roji mentioned this pull request Aug 20, 2022
53 tasks
@roji roji disabled auto-merge August 20, 2022 13:42
@ghost
Copy link

ghost commented Aug 20, 2022

Hello @roji!

Because this pull request has the auto-merge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

@ghost
Copy link

ghost commented Aug 20, 2022

Apologies, while this PR appears ready to be merged, I've been configured to only merge when all checks have explicitly passed. The following integrations have not reported any progress on their checks and are blocking auto-merge:

  1. Azure Pipelines

These integrations are possibly never going to report a check, and unblocking auto-merge likely requires a human being to update my configuration to exempt these integrations from requiring a passing check.

Give feedback on this
From the bot dev team

We've tried to tune the bot such that it posts a comment like this only when auto-merge is blocked for exceptional, non-intuitive reasons. When the bot's auto-merge capability is properly configured, auto-merge should operate as you would intuitively expect and you should not see any spurious comments.

Please reach out to us at [email protected] to provide feedback if you believe you're seeing this comment appear spuriously. Please note that we usually are unable to update your bot configuration on your team's behalf, but we're happy to help you identify your bot admin.

@ghost
Copy link

ghost commented Aug 20, 2022

Apologies, while this PR appears ready to be merged, it looks like release/7.0-rc1 is a protected branch and I have not been granted permission to perform the merge.

{
builder.ToTable(table.Name, table.Schema, tb => tb.HasTrigger(triggerName));
builder.ToTable(table.Name, table.Schema, tb => tb.HasTrigger(trigger.Name));
Copy link
Contributor

Choose a reason for hiding this comment

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

Copy annotations too?

Copy link
Member Author

Choose a reason for hiding this comment

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

Good point, thanks.

@ghost
Copy link

ghost commented Aug 20, 2022

Apologies, while this PR appears ready to be merged, it looks like release/7.0-rc1 is a protected branch and I have not been granted permission to perform the merge.

@ghost
Copy link

ghost commented Aug 21, 2022

Apologies, while this PR appears ready to be merged, I've been configured to only merge when all checks have explicitly passed. The following integrations have not reported any progress on their checks and are blocking auto-merge:

  1. Azure Pipelines

These integrations are possibly never going to report a check, and unblocking auto-merge likely requires a human being to update my configuration to exempt these integrations from requiring a passing check.

Give feedback on this
From the bot dev team

We've tried to tune the bot such that it posts a comment like this only when auto-merge is blocked for exceptional, non-intuitive reasons. When the bot's auto-merge capability is properly configured, auto-merge should operate as you would intuitively expect and you should not see any spurious comments.

Please reach out to us at [email protected] to provide feedback if you believe you're seeing this comment appear spuriously. Please note that we usually are unable to update your bot configuration on your team's behalf, but we're happy to help you identify your bot admin.

@ghost
Copy link

ghost commented Aug 21, 2022

Apologies, while this PR appears ready to be merged, it looks like release/7.0-rc1 is a protected branch and I have not been granted permission to perform the merge.

@roji roji merged commit 585b434 into dotnet:release/7.0-rc1 Aug 21, 2022
@roji roji deleted the ScaffoldedTrigger2 branch August 21, 2022 10:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants