BulkUpdates: Add custom CommandSource and exception messages #28583
Conversation
|
Hello @smitpatel! Because this pull request has the 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 (
|
|
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:
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 thisFrom the bot dev teamWe'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 fabricbotservices@microsoft.com 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. |
| /// <summary> | ||
| /// The command was generated as part of an 'ExecuteDelete' operation. | ||
| /// </summary> | ||
| ExecuteDelete = 9, |
There was a problem hiding this comment.
Is it intentional to explicitly set a value only here? I don't think we need explicit enum values here in general, but if we do, shouldn't we do it for all values?
There was a problem hiding this comment.
I added here so that if we accidentally remove the obsolete value, the enum doesn't change values.
There was a problem hiding this comment.
cc: @AndriySvyryd - Thoughts?
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
ghost
merged commit 
Resolves #28568