Skip to content

Conversation

@ntacheva
Copy link
Contributor

@ntacheva ntacheva commented Nov 21, 2024

And code style fixes.

@ntacheva ntacheva added the merge-to-production Use this label to get a comment to choose whether to merge the PR to production label Nov 21, 2024
@ntacheva ntacheva self-assigned this Nov 21, 2024
@ntacheva ntacheva requested a review from a team as a code owner November 21, 2024 09:11
@github-actions
Copy link
Contributor

Hello @ntacheva,

Check the below option if you would like to automatically generate PR to production. The automation uses the branch for the cherry-pick, and then will delete the branch. Please, do not delete it manually.

  • create PR to production

Copy link
Contributor

@dimodi dimodi left a comment

Choose a reason for hiding this comment

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

We can also add this note before the example for better visibility. Otherwise the customer may hit the error first.

@ntacheva ntacheva merged commit f01cf67 into master Nov 21, 2024
1 check passed
@github-actions
Copy link
Contributor

Here you are the link to your PR to production: 2554

@github-actions github-actions bot deleted the ntacheva-patch-1 branch November 21, 2024 12:14
VelinovAngel pushed a commit that referenced this pull request Nov 26, 2024
* chore(grid): clarify the required DotNetObjectReference type

* chore(common): add note
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merge-to-production Use this label to get a comment to choose whether to merge the PR to production

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants