Skip to content

Conversation

@ntacheva
Copy link
Contributor

No description provided.

@ntacheva ntacheva self-assigned this May 16, 2025
@ntacheva ntacheva requested review from a team as code owners May 16, 2025 09:58
@ntacheva ntacheva added the merge-to-production Use this label to get a comment to choose whether to merge the PR to production label May 16, 2025
@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.

Better replace getting-started/server-side with getting-started/web-app instead of removing it

@matanasov matanasov merged commit f35dbc0 into master May 16, 2025
@github-actions
Copy link
Contributor

Automatic cherry-pick & PR to production failed. Ping @telerik/blazor-admins for manual cherry-pick and push to production.

@github-actions github-actions bot deleted the fix-broken-slugs-2 branch May 16, 2025 12:10
Copy link
Contributor

@ikoevska ikoevska left a comment

Choose a reason for hiding this comment

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

🚀

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.

5 participants